Forum Discussion

jackwagner11's avatar
jackwagner11
New Contributor
3 months ago
Solved

Unable to Complete Workflow due to Security Access

Hello OneStream Community, 

I am running into an issue with the ability to complete a workflow with a dashboard button as a test security user.  Any help would be greatly appreciated.  

I have a consolidation status dashboard, which is attached to the top-most workflow node for a given month.  My issue is as a test end-user I keep receiving the following error message when attempting to complete the Workspace chevron and move on to the certify step of the workflow.  

The security settings for the workflow are very simple, so it's not clear what could be the issue here.

Is there another way I could get around this?

  • The solution was creating a button that uses a Business Rule, rather than the standard Button Type of "Complete Workflow", unfortunately using the standard button type does not allow users to complete workflows with security assignments, however the business rule does allow for it.  

    I attached the below button type to my dashboard and it worked.  I had to write a business rule to perform the completion but at least I'm not getting the security error anymore.

     

2 Replies

  • jwagner's avatar
    jwagner
    New Contributor III

    The solution was creating a button that uses a Business Rule, rather than the standard Button Type of "Complete Workflow", unfortunately using the standard button type does not allow users to complete workflows with security assignments, however the business rule does allow for it.  

    I attached the below button type to my dashboard and it worked.  I had to write a business rule to perform the completion but at least I'm not getting the security error anymore.

     

  • MarcusH's avatar
    MarcusH
    Valued Contributor

    Without seeing the BR behind the Complete WF button it is difficult to diagnose. I have had a similar problem and the same error message when a BR was executing the function GetCubeInfo. The BR just needed the Cube ID so I used a SQL statement instead. I would add some debug messages to the error log to try and understand if it is an API call that is raising the error.