So I am trying out Plumber (1.1.3) and have created a rather simple worlkflow.
For a specific page type I have three groups
Creators => 2. Reviewers => 3. Approvers.
I have assigned 3 users to these groups but get lost in what permissions are needed for Plumber to do its magic.
As of now the creator only has Browse, Create & Update Permission which doesn't seem to work. After creating the page of said page type I can't push it forward.
According to the documentation Plumber overrides Umbraco's publish rights so I wonder what would be the correct permission setup for the three users.
Given that creators should only be able to create, reviewers do nothing but send forward and approvers able to publish if approved by reviewers.
There shouldn't need to be any modification to the Umbraco defaults - your workflow could go through the three group, and if you have the lock active content setting set to true, the subsequent groups won't be able to modify the page when it's in the workflow.
What happens when you try to send the page into the workflow? Any visible errors in the console, unresponsive UI etc?
Thank you for responding. No, I get no error message.
For the admin user, I can use the request publish but for the users in group 1 (Creators) I can only save. The workflow tab is empty for those users.
I have the lock active content active but tried without it as well.
I am running a cloud site if that helps.
And no no error message besides when I try to export the config then i get:
Exception Details
ArgumentNullException: Error exporting workflow configuration
Stacktrace
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
at Plumber.Core.Mapping.SettingsMap.Map(WorkflowSettingsPoco src, WorkflowSettingsViewModel dest, MapperContext ctx)
at Umbraco.Core.Mapping.UmbracoMapper.<>c__DisplayClass8_0`2.<Define>b__1(Object source, Object target, MapperContext context)
at Umbraco.Core.Mapping.UmbracoMapper.Map[TTarget](Object source, Type sourceType, MapperContext context)
at Umbraco.Core.Mapping.UmbracoMapper.Map[TTarget](Object source, MapperContext context)
at Plumber.Core.Repositories.Implement.ImportExportRepository.ExportSettings()
at Plumber.Core.Services.Implement.ImportExportService.Export()
at Plumber.Web.Api.ImportExportController.<Get>d__3.MoveNext()
I'm having a similar issue - I have created a workflow with just one approval group for test purpose.
In that approval group I have added an admin user and another user with Editor permission.
Once the document is in the workflow - only the admin user can action the wrokflow. It displays the below message for the other users in that approval group.
Jakob - you're correct, if the user doesn't have publish permissions, they won't be able to advance a workflow. I'll fix that to allow anyone in the workflow group. Currently it's throwing a JS error because there are no buttons for the user.
Charlene - I can't reproduce that issue. I've created a workflow with a single group, with two members, one an admin, one an editor. Both can approve pending tasks in that workflow. Have you made any changes to the default permissions for the editor group? Which Plumber flow-type are you using?
EDIT - the permissions issues was kinda not really permissions, but a null error in the javascript. I'll commit the fix, but won't have a release out for a little while as I have a rewrite of the entire backoffice JS application pending, so need to test that properly. Nightly will still build, feel free to install and see if it works. Might work, might not work...
There's a bug in the licensing popup, fixed in the next release. When that bug is resolved, the popup includes the stripe payment form.
As for release dates, it will be done when it's done - it's a substantial testing effort for the javascript changes (updating everything to es6 modules, using gulp instead of grun) so will take a bit of time.
Ok, would be much appreciated if you update me on an ETA when you think you have one. I would really like to try out the Offline approval as well.
Totally of the topic, It feels a bit strange that you can "Request For publish" when you have unsaved changes. It would feel more natural to have the same default alert as when you navigate away from a page with unsaved changes. Just a thought.
What user permissions should I use?
Hi
So I am trying out Plumber (1.1.3) and have created a rather simple worlkflow. For a specific page type I have three groups
I have assigned 3 users to these groups but get lost in what permissions are needed for Plumber to do its magic.
As of now the creator only has Browse, Create & Update Permission which doesn't seem to work. After creating the page of said page type I can't push it forward.
According to the documentation Plumber overrides Umbraco's publish rights so I wonder what would be the correct permission setup for the three users.
Given that creators should only be able to create, reviewers do nothing but send forward and approvers able to publish if approved by reviewers.
Br/ Jakob
Hi Jakob
There shouldn't need to be any modification to the Umbraco defaults - your workflow could go through the three group, and if you have the
lock active contentsetting set to true, the subsequent groups won't be able to modify the page when it's in the workflow.What happens when you try to send the page into the workflow? Any visible errors in the console, unresponsive UI etc?
Hi Nathan
Thank you for responding. No, I get no error message.
For the admin user, I can use the
request publishbut for the users in group 1 (Creators) I can only save. The workflow tab is empty for those users.I have the
lock active contentactive but tried without it as well.I am running a cloud site if that helps.
And no no error message besides when I try to export the config then i get:
Exception Details
Hi,
I'm having a similar issue - I have created a workflow with just one approval group for test purpose.
In that approval group I have added an admin user and another user with Editor permission.
Once the document is in the workflow - only the admin user can action the wrokflow. It displays the below message for the other users in that approval group.
Two part response...
Jakob - you're correct, if the user doesn't have publish permissions, they won't be able to advance a workflow. I'll fix that to allow anyone in the workflow group. Currently it's throwing a JS error because there are no buttons for the user.
Charlene - I can't reproduce that issue. I've created a workflow with a single group, with two members, one an admin, one an editor. Both can approve pending tasks in that workflow. Have you made any changes to the default permissions for the editor group? Which Plumber flow-type are you using?
EDIT - the permissions issues was kinda not really permissions, but a null error in the javascript. I'll commit the fix, but won't have a release out for a little while as I have a rewrite of the entire backoffice JS application pending, so need to test that properly. Nightly will still build, feel free to install and see if it works. Might work, might not work...
Hi Nathan,
Thanks for the response - I reset the Editor user permissions and it is working now.
Thanks :)
Hi Nathan
When do you think you will have the next real version out? Also When trying to create a real subscription from within Umbraco it only says:
I am interested in a one time fee. How to progress?
Hi Jakob
There's a bug in the licensing popup, fixed in the next release. When that bug is resolved, the popup includes the stripe payment form.
As for release dates, it will be done when it's done - it's a substantial testing effort for the javascript changes (updating everything to es6 modules, using gulp instead of grun) so will take a bit of time.
Hi Nathan
Ok, would be much appreciated if you update me on an ETA when you think you have one. I would really like to try out the Offline approval as well.
Totally of the topic, It feels a bit strange that you can "Request For publish" when you have unsaved changes. It would feel more natural to have the same default alert as when you navigate away from a page with unsaved changes. Just a thought.
is working on a reply...