If you take a page and put it in a workflow, then if someone wants to modify that page – in an emergency situation and essentially start another workflow on it –
Is that possible to send that page through another workflow?
If you don’t want to send the same page through a workflow, but just want to edit it, can you?
Apparently If one person is editing a CQ page and same page is edited by someone else at the same time, at production level, how the CQ / developer handles the situation?
Thanks in Advance
It is not possible to subject a page to more than one workflow at once, none of the interfaces allow this to happen.
The pages can be edited even when they are subject to a workflow. In emergency situations where in it is not possible to complete the workflow , users with required privileges can terminate the workflow from the instances tab of the workflow console (/libs/cq/workflow/content/console.html). Pages can be usually activated even if they are subject to workflows.
The repository is accessed via repository session. Based on the credentials provided the user gets a repository session. Any changes made via that session is only visible to the other users when the session is saved. Since different sessions are used , multiple users can edit the same page simultaneously. The data in dialogs are loaded via asynchronous GET requests when EDIT is clicked and not on page load , so it is very unlikely that the user will be editing old data. They can still overwrite some other user's changes. Developers do not have to handle these situations unless there is some special requirement. If a user wants to stop other users from editing a page , they can use the lock functionality that comes out of the box. A locked page can be unlocked only by the user who locked it or an administrator. A page or node can be programmatically locked via the JCR API.
Related
I need a setup where users can update a page and then submit it for approval/activation in AEM 6.2. The page would be submitted to workflow where a content approver/administrator would review and publish the page. This seems like a common setup for content managment, but I can't figure out how to do it in AEM.
I have done the following:
setup a user that has permission to update but does NOT have
replicate permission on folderX.
setup users with update and replicate permissions on folderX and added them to a group "content-authors-approvers"
created a workflow where the first step of the workflow is the page will be submitted for approval and publication to member of "content-authors-approvers" group
assigned this workflow to folderX
However, when a user does NOT have replicate permission, the "publish" option does not show up at all. This makes sense, really....but then, how does one go about setting up a workflow like this?
From what I've read about this in earlier versions of AEM/CQ5, the replicate/publish option was still available to all users, but it would automatically kick off workflow if the user did not have replicate permissions. (see Start a workflow on page activation without activating the page in CQ5 )
this seems to have changed in 6.2. can anyone help?
I have tried looking up online, but found nothing
There is a native workflow to handle that. It's named Publish Example. see it here: http://localhost:4502/etc/workflow/models/publish_example.html . I believe that it's better then the automatic triggering cause the author actually knows he triggers a workflow (whilst when it happened automatically there was no info about that). To explicitly call it you have to either from /siteadmin select a page and click workflow on it, or do it from sidekick or in touch.
sidekick:
touch - editpage:
I've implemented a custom workflow in Adobe CQ5.6, similar to http://blogs.adobe.com/learningwem/2011/11/30/cq5-4-workflow-example-approve-reject-by-the-reviewer/
I'm using CQ5 inbox notifications only -- no email notifications.
The problem is, after the Approver selects either "Approve" or "Reject", the inbox notification does not get removed, even though the workflow continues / completes.
There doesn't seem to be an option to manually delete a notification, unless you go into crxde and delete the nodes. So the main concern here is that notifications will quickly pile up, making it confusing to figure out which ones are current, and ultimately clogging up the app.
This only seems to happen at this exact step in the workflow. The Author's notifications disappear once they've been dealt with, as you would expect.
Has anyone had anything like this happen before?
Something about the way I worded this question helped me figure out the answer.
The Author's notifications disappear ... as you would expect
This made me think it might be a user permission problem rather than anything to do with the workflow step.
I confirmed this by switching the roles of the two user types, (so the Approver starts the workflow and the Author must approve the change). As I guessed, it was any notification assigned to the Approver, rather than notifications generated by that particular workflow step, which were not disappearing.
Specifically, the permission that was missing was for /etc/workflow/instances. I allowed all methods for that user, and my problem is resolved.
You can edit permissions via /useradmin.html in your CQ5 instance (in my case, http://localhost:4502/useradmin.html )
We are trying to implement a custom checkout policy for a Plone Document Management System. In this, we would like to be able to have Working Copies of published documents after a certain period of time.
Iterate seems perfect for this.
However, we only want the checkout to be available for published documents. So here is the reasoning....
Since the workflow controls several permissions, we added both "iterate : Check in content" and "iterate : Check out content" to the permissions tab in the portal_workflow tool.
We then marked the checkboxes in the permission tabs of the individual workflow states for those people who have checkout rights.
However, in the frontend, everybody keeps having the option to checkout documents regardless of the state the document is in.
What are we missing?
PS: We already checked out the document on "Working Copy Workflow Customization" and in our opinion this relates to changing the workflow for checked out documents, which is not what is intended here...
The problem here I think is the checkout_allowed method in plone.app.iterate/browser/control:Control.
It doesn't check on any permissions before allowing checkout for the user(it assumes if they user can view it, they should be allowed to check it out to home folder and such--I guess that's a reasonable use case).
Then, in the portal_actions/object_buttons/iterate_checkout it simply uses the "View" permission to allow the button to be placed there.
So to be completely correct for this, you would have to customize the checkout_allowed method and the permission used in the action.
To do it quick and simple so the user just doesn't see the button, change the button permission to "iterate: checkout content".
I just got starte with programming a Facebook app. I already wrote an app for the VZ-Network, and there they have something called 'Persistant Storage'. Basically its an environment where you can save custom data on each user account. With your app you can read this data from the current user as well as from the users friends. Now I want to port my app to Facebook and my problem is that I didn't find such functionality here yet.
For now I would like to finish and launch this as soon as possible, so it would be nice if I could c&p as much of the code as possible.
Since the data is contains information about participation, at some point I would like to use the Facebook event object. But I was wondering if that could cause problems since it would require to create those events publically in order to use them in my app. Couldn't that lead to legal problems when I create such events with those who actually host the events in the real world? Would I have to ask the hosts to create those events, could I automate this process, or in case they don't have a Facebook account ask them to approve that the app creates the event for them?
I also need to know in what events the users friends participate, so I can't simply save the information on my server, since I don't have the friend info there.
In any case, it seems much easier to me to simply use a list of EventIDs on each user account to check whether or not the user participates in an event.
I’ve designed a form for a user here to collect data for a workflow. I used SharePoint designer to build a custom approval form. When the workflow is initiated I am receive and email to ‘Edit Task’. I click on the Edit Task button and it takes to the form. I enter the information requested and my tasks lists and calendar are updated. However when I set the email to go to the user who will be entering the data( approval) the ‘Edit Task’ Button takes him to an error page “404 page not found”.
It seems that when I created the form SharePoint saved it to a local server and not to the Sharepoint server. I notice that the out of the box workflows go to this directory: http://vaww.visn16.portal.va.gov/sites/HOU/IMS/VistA/Help/_layouts/...
However my form is in the Workflow directory: http://vaww.visn16.portal.va.gov/sites/HOU/IMS/VistA/Help/Workflows/
I use my Explorer to go to My Network Places and I can see the directory for my workflow and workflow form. However other users with my same permission can get to the Workflow directory but only they cannot see the form. The other files associated with the workflow are present for them. Why can’t others access(see) the form? Users that I have asked to test this workflow all have full permissions like me.
Make sure the page that you navigate to when you click the Edit Task button is not checked out to you. If it is checked out, check it in and others should be able to see the page.