Forum Discussion

THENDRICKSON's avatar
THENDRICKSON
Contributor
2 months ago

Security for Workflow Multi-Period Processing

We are attempting to upgrade the Financial Close Marketplace Solution from version PV640 SV100 to PV710 SV201. We are on platform version 7.2.4. 

We have a group of SuperUsers (similar to an Admin role but with less access than an Admin) that should be able to access and execute batches for the Workflow Multi-Period Processing page. (screenshot attached). They can access the page, but the Execute Batch button is greyed not allowing them to execute any of the steps. They have this ability in the environments where the solution has not been upgraded yet. 

I cannot find anywhere in the workflow profile or business rules where security is being referenced for this Execute Batch button. 

Can anyone guide me in the right direction to allow them to have access to that button in the upgraded solution? 

Workflow
  • KarlT's avatar
    KarlT
    Contributor III
    2 months ago

    Maybe check this setting in Security Roles in both applications/environments (sorry ignore this, i see Ioana already suggested this!)

     

  • THENDRICKSON's avatar
    THENDRICKSON
    Contributor
    2 months ago

    Ioana Thank you for responding. 

    1. Yes, I did check Security, and it set correctly. 

    2. Unlocking the Parent first still does not give the user access to the "Execute Batch" button. It is still greyed out for them. I even tested for one month. 

    • T_Kress's avatar
      T_Kress
      Contributor III
      2 months ago

      If there were no security changes between versions then it should not be security related but here are the 3 security roles that impact the batch execution:

       

      As you can see, in addition to these security roles a person would also need Access, Execute and Certify to the particular workflow(s) in order to perform the batch execute.

      I still think if the button is greyed out, more than likely it has something to do with an ancestor or descendant that is still locked, preventing the batch process from being able to run.  You cannot execute certain steps like Import, Validate, Load or Process if children or ancestors workflows are locked.

      I think more than likely that is the root cause.

  • Ioana's avatar
    Ioana
    New Contributor III
    2 months ago

    Hello,

    I see you are trying to unlock import wf profiles. I would check the following:

    1) Have you checked the Security assigned to UnlockWorkflowUnit found in the Application tab - Tools - Security Roles?

    2) I tested in one of my applications and it seems I cannot unlock descendants if the Parent profile (CDF_Input in your case) is locked for the period. Try unlocking it first and then try to unlock the imports.

    I would test for one month first.

    Thanks,

    Ioana