roberth55706517 wrote... alvawb1 wrote... If this is for AEM 6.1, then there are some security changes from how it was implemented in 6.0. In 6.1, for users in projects to see other users/groups while using Projects functionality like creating projects, creating tasks/workflows, seeing and managi...

alvawb1 wrote... If this is for AEM 6.1, then there are some security changes from how it was implemented in 6.0. In 6.1, for users in projects to see other users/groups while using Projects functionality like creating projects, creating tasks/workflows, seeing and managing the team, those users nee...

I logged in as myself instead of the administrator. Even though I'm in the administrators group, I couldn't see the information. When when I logged in as the administrator, I could see the data. Figure that one.

Where is the team information stored?We have a servlet that creates projects and then builds out permission sets and workflows to manage tasks associated with the project. If the standard "Create" link is clicked on the project.html page, then the project is created but the details can only be viewe...

The log level is at debug.The session is being created thus:Session session = resourceResolver.adaptTo(Session.class);This is in a servlet that overrides SlingAllMethodsServlet.

The user agent should have full access to that. I'll have to check the permissions. Shouldn't there be an error in the logs?try { JSONArray jsonData = new JSONArray(data); for( int i = 0; i < jsonData.length(); i++){ JSONObject obj = jsonData.getJSONObject(i); String path = folder + "/" + obj.getStr...

I was able to add this, sort of. The problem was that the rejection didn't save unless the step was completed. Since the approve and reject are separate options, if I rejected an image, then approved, the rejected mages would be reset to "pending". I was using an ajax call to a servlet I wrote to se...

That did work for what I need with that step.Now how about a link that fully explains the OR join/split step? I've searched but only find mentions of it.

This implementation has been heavily customized. There isn't a back option it is the fifth step of six where the reject occurs and it has to jump back to the second step and proceed from there until the reviewer accepts all of the assets.

They client creates a project that starts off a workflow. The work flow progresses along until an approval step. At that point they want to be able to reject asset(s) and return the processing to a previous step then proceed normally from there, retracing the steps between. Since there is an approva...