Getting Started 
Trainings 
News 
FAQs 
Webinars Configuration Version – URS
User Requirments Specification
List of requirments needed to be tested in order to validate the process.
Click on the requirement to edit the wording.
The URS is divided to sections. After the first two sections, each section is related to a different status in the record.
A requirement that is not necessary- mark as N/A (Not Applicable) and add a reason it will be grayed out and won’t be checked in the UAT.
Configuration Version – UAT
User Acceptance Testing
Steps that are to be made in order to test the process in Simploud through the required functionalities presented in the URS
Configuration Version - Workflow
Configuration Version - Workflow
This step is used for designing the process to your own needs. Each process in Simploud is pre-designed using industry best practices but you can change it to fit your company’s business requirements.
All you need to do is to request changes by opening a configuration item under the Configuration Item tab. Simploud Success will implement your request (if possible) and the changes will be reflected in the URS/UAT after clicking Send for Testing.
After moving to this stage, the minor version increases (e.g., 0.1 to 0.2) and new versions of the URS and UAT are created automatically.
This step is used for testing the changes performed by Simploud Success. The following steps are recommended to avoid errors or script deviations:
1. Review the newly created URS and UAT to check that your new changes have been applied.
2. If needed, you can apply changes to the auto generated text of the URS/UAT by clicking on the rows you need to change.
3. Add additional requirements and tests that are missing in the URS/UAT by clicking on the Requirements option below.
4. Perform a dry run on the UAT by clicking on the execute test *Explanation in the next slide.
Workflow- Testing Status
Dry Run: We recommend doing a dry run before moving to the validation status in order to check that all the tests are updated.
Click on execute UAT and follow along the instructions and see that there are no gaps in the validation.
! If changes were made, they will show on the next execute test (there is no limitations on how many execute tests a user can perform).
! If there are changes that you made in the Design status and you still don’t see the updated requirements in the Testing status, you can click on the ”Recreate process documentation” to make sure the URS & UAT are updated with the latest configuration details.
Configuration Version - Workflow
You got to the official validation step: Here you will electronically sign the URS/UAT/TMX and complete your UAT execution electronically.
After clicking on the Passed Validation you will be requested to add the validation conclusion that will be appended to the validation certificate.
1. Sign the URS
2. Sign the UAT and click on the Execute Test button (Once signed, you’ll be able to execute tests). *Explanation in the next slide.
3. Sign the TMX
4. After clicking on the Passed Validation you will be requested to add the validation conclusion that will be appended to the validation certificate.
Configuration Version - Workflow
What happens if a deviation failed? We recommend that before opening a deviation, open a configuration item and only then, if needed, open a deviation.
Once a deviation is opened, you can’t run another test execution.
Configuration Version - Workflow
Congratulations! You’ve passed the validation and are ready to go live with your changes. There might be some additional steps required to give your users the proper access to this process.
Please open a configuration item so the Simploud Success team will complete the migration activities and let you know what is required from your end.