Forum Stats

  • 3,770,165 Users
  • 2,253,079 Discussions
  • 7,875,353 Comments

Discussions

Restricting User access to data post data submission

3910382
3910382 Member Posts: 8
edited Sep 18, 2020 10:16AM in Planning and Budgeting

Hi,

Hope you all have been keeping well.

We have a requirement where in the ask is to make the form content ( basically all of the form) readonly once the user submits the data. Once submitted, the user should not be able to change the submitted data set.

Is there a way to achieve this without introducing workflow? Reason being, the PBCS application is only serving the purpose of data capture to be sent to PCMCS for allocations. Hence would like to avoid workflow.

Your help/suggestions are much appreciated

Thank you !

Tagged:
3910382Robert Angel

Answers

  • Robert Angel
    Robert Angel Member Posts: 4,535 Bronze Crown
    edited Sep 17, 2020 3:27PM

    One way to do this is using version.

    Initial populate your data into a version called (say) Working, on post of the data in the form use the current members to copy the data from that version to a version called (say) Committed, in the form in question show only the data in Working and have it as data entry, in the next read only form have the Committed version, or you could even have both in the same form and restrict direct data entry into Committed by using security (which the business rule is not affected by) or by closing it for the year / periods in questions (which the business rule also ignores).

  • 3910382
    3910382 Member Posts: 8
    edited Sep 17, 2020 3:41PM

    Thanks Rob!

    In the proposed solution, user can still edit the numbers on the form with working version post the initial submission! from a controls stand point that is something we want restricted for the user!

  • Robert Angel
    Robert Angel Member Posts: 4,535 Bronze Crown
    edited Sep 17, 2020 3:47PM

    Hi,

    I am suggesting that you put a business rule on the input form that is invoked by 'save' action, such that it copies the data to another version, and deletes the data from the (open to all) working version.

    And it is Robert.

    3910382
  • 3910382
    3910382 Member Posts: 8
    edited Sep 17, 2020 3:50PM

    Thanks Rob

    Thats a viable solution.

  • 3910382
    3910382 Member Posts: 8
    edited Sep 18, 2020 4:26AM
  • Rahul S
    Rahul S Practice Director - EPM Member Posts: 1,777 Gold Trophy
    edited Sep 18, 2020 10:16AM

    I would still stick with a simple workflow because it's hard to find the automatic trigger for making forms read-only and workflow is designed for that. What if someone has entered wrong data and wants to correct that, would you want to restrict data input after the first save?. Users should drive when they are ready to submit the allocation rates. If not workflow, you can either create a batch or groovy to update security and give execution access to user to be triggered when they are ready to commit the data load.

    Rahul S.