Forum Discussion

RobbSalzmann's avatar
RobbSalzmann
Valued Contributor II
3 years ago

Re: Application Security Role update with Business Rules

Thanks JackLacava .  To put a little more structure around this, the requirement is to lock a scenario (using a button) for a period of time, then set it back to its original access with another button.

Use Case:
An all day meeting with the CFO commences to discuss and refine a forecast.  During this meeting the scenario needs to be locked down to prevent a potential moving target, changing values.  When the meeting is over the scenario is opened back up and FAs are given tasks to update the forecast.
The admin wants a simple set of on/off buttons to accomplish the locking/unlocking of the scenario.

9 Replies

  • cjohnson's avatar
    cjohnson
    New Contributor III
    3 years ago

    Would locking/unlocking the workflow not be a valid approach for this?

    • mvalerio24's avatar
      mvalerio24
      Contributor
      3 years ago

      I dont think so, we aren't trying to lock a scenario down. We are basically trying to change the write group on a scenario so certain users can't make any changes for a certain amount of time and then change it back after. I've tried using code to update the read and write group but id doesn't seem to update in OS, only on the backend.

      • JackLacava's avatar
        JackLacava
        Honored Contributor
        3 years ago

        Security changes will typically need a refresh of some sort - app refresh, page refresh, logout/login,  etc - before they are reflected consistently in every corner of the UI. Beyond that, it should all work; if there is some other problem with the API mentioned, maybe it should be reported to Support.