reapit/foundations

Data being lost post saving via licensing screen

Opened this issue · 6 comments

Describe the bug
Data entered in the ‘Current licence application’ fields on Yuno licensing screen are not saving.
We have noticed that once we click on save and then save the property records, when you go back into the licensing screen it reverts back to what was on there before.

To Reproduce
We've recreated this as follows.

  1. Open a test property
  2. Open the licensing screen
    Update the 'Application Status'
    Hit 'Save'
    Close the licensing screen
  3. Check the updated licensing data using GET /properties/{id}
  4. Open the licensing screen
    Check the 'Application Status' has not reverted
    Close the licensing screen
  5. Update any field on the property screen that is stored in PRP.EXTRA e.g. pLldRespChkIn=.T.
  6. Exit the property record
  7. Open the test property again
  8. Open the licensing screen
    Licensing data has been reset

Expected behaviour
Don't delete the data.

Screenshots
image010

Thank you for taking the time to report a bug. We prioritise bugs depending on the severity and implications, so please ensure that you have provided as much information as possible. If you haven’t already, it really helps us to investigate the bug you have reported if you provide ‘Steps to Replicate’ and any associated screenshots.
Please ensure any personal information from the production database is obscured when submitting screenshots.
This issue will be reviewed in our weekly refinement sessions and assigned to a specific project board. We may also update the ticket to request additional information, if required.
For more information on our processes, please click here

Hi @GoYuno please can you just confirm that steps 2 and 4 are completed in the Yuno app rather than the native licensing screen in AgencyCloud?

Correct.

Thanks - this is due to how AgencyCloud is operating in conjunction with apps launched inside it and it looks like a missing or malfunctioning optimistic concurrency mechanism. I know there is already a service item raised for this same issue which I was made aware of earlier today and will use this information to liaise with the AgencyCloud product team.

As this issue relates to AgencyCloud, we are unable to process this through the Platform in accordance with our Developer Processes.
Issues relating to AgencyCloud should not be submitted via the Foundations GitHub repo but should be raised via the Reapit Service Desk by a Reapit Customer.
Please ask a Reapit Customer to raise this issue via the Reapit Service Desk.
For more information on our processes, please click here