Skip to main content

RADplus 2023 Update 80

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2023 Monthly Release 2023.02.00

Product Update Description

Auditing fields are added to the 'SYSTEM.radplus_envelope_info' table.

Required Updates

None

Included Updates

2, 4, 6, 12, 22, 25, 26, 29, 33, 35, 49, 55, 56, 58, 59, 64

Details

NEW1 CHANGED0 FIXED0
New (1)
Modeling - 'SYSTEM.radplus_envelope_info' table
Auditing fields are added to the 'SYSTEM.radplus_envelope_info' table, to provide a record of when a modeled "Envelope" is updated
Value Added: Provides a user to ability to check if an envelope has been modified
Topics
• Modeling • NX • SQL Data Access
 
Acceptance Tests

AV-90500 Summary | Details
Modeling - 'SYSTEM.radplus_envelope_info' table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Caseload Type Definition (PM)
  • Change Envelope Build Environment (PM)
  • Data Element Help Message Definition (PM)
  • Dictionary Export (PM)
  • Dictionary Import (PM)
  • Dictionary Update (PM)
  • Document Routing Setup (PM)
  • Dynamic Form - Caseload Type Definition - Select Existing Caseload Type
  • Dynamic Form - Document Routing Setup - Select Form
  • Envelope Merge (PM)
  • Form Deletion (PM)
  • Form Designer (PM)
  • Form Signature Authentication (PM)
  • Import Reports (PM)
  • Notification Type Definition
  • Report Definition (PM)
  • Report Definition Export
  • Report Definition Import (PM)
  • Table Definition (PM)
  • Table Deletion (PM)
Scenario 1: Validate (Audit Field) data in the 'SYSTEM.radplus_envelope_info' SQL Table View
Specific Setup:
  • Have the following "modeled" envelopes created:
  • [TestEnvelopeA] contains a modeled table [TestTable] and modeled form [TestForm] that includes a "Scrolling Free Test" field, a "Draft/Final" field, a "Dictionary" field and any other desired field types
  • [TestEnvelopeB] contains a modeled table [TestTableB] and modeled form [TestFormB] that includes any desired field types and no data has been filed in the form yet
  • [TestEnvelopeC] contains a modeled table and modeled form that includes any desired field types
  • In form "Envelope Export", export [TestEnvelopeB] and store the export file in a folder
  • The user [TestUser] has permissions assigned to query table view 'SYSTEM.radplus_envelope_info' in their user definition
  • Have a report [TestReport] created to display field data in the 'SYSTEM.radplus_envelope_info': table
  • In form "Import Reports", have a report [ImportReport] imported as import type "Import Report for command button launch
  • Log in as [TestUser]
Steps
  1. Open form "Envelope Definition"
  2. Select [TestEnvelopeA]
  3. Make any change and submit the form or just submit the form without any changes
  4. Validate submission is successful. (Note the current date and time)
  5. Run [TestReport]
  6. Validate the following audit fields are populated as expected for the form just submitted, based on the submission date/time noted and the user submitting the form:
  7. "data_entry_by", "data_entry_by_option", "data_entry_user_id", "data_entry_user_name", "data_entry_option", "data_entry_source", "data_entry_date", "data_entry_time"
  8. In addition, if "UTC" time is enabled on the system, validate the following fields are populated as expected:
  9. "data_entry_utc", "data_entry_timezone_info_all", "data_entry_time_j", "data_entry_offset", "data_entry_timezone_short"
  10. Open form "Form Definition"
  11. Select the modeled form [TestEnvelopeA]
  12. Make any change to the form or just submit the form without any changes
  13. Validate submission is successful. (Note the current date and time)
  14. Repeat step 2
  15. Validate results are as expected
  16. Open form "Table Definition"
  17. Select the modeled table [TestTableA]
  18. Make a change and submit the form or just submit the form without any changes
  19. Validate submission is successful. (Note the current date and time)
  20. Repeat step 2
  21. Validate results are as expected
  22. Open form "Document Routing Setup"
  23. Select [TestFormA]
  24. If the form is already enabled for document routing, just submit the form, if not, then enable the form for document routing and submit the form
  25. Validate the form submits successfully (Note the current date and time)
  26. Repeat step 2
  27. Validate results are as expected
  28. Open form "Data Element Help Message Definition"
  29. In the "File" field, select the "File" used in envelope [TestEnvelopeA]. For example, the "User Defined Client" file
  30. In the "Data Element" field, select one of fields used on form [TestFormA]. For example, the dictionary field
  31. Enter any text in the "Data Element Help Message'
  32. Submit the form
  33. Validate the form submits successfully (Note the current date and time)
  34. Repeat step 2
  35. Validate results are as expected
  36. Open form "Scrolling Free Text Templates"
  37. Select the modeled table [TestTableA]
  38. In the "Template Definition" section add a row and select the "Scrolling Text Field"
  39. Populate the required fields and submit the form
  40. Validate the form submits successfully (Note the current date and time)
  41. Repeat step 2
  42. Validate results are as expected
  43. Open form "Envelope Merge"
  44. Select [TestEnvelopeA]
  45. In field "Envelope to Merge into Current Envelope", select [TestEnvelopeC]
  46. Submit the form
  47. Validate the form submits successfully (Note the current date and time)
  48. Repeat step 2
  49. Validate results are as expected
  50. Open form "Form Designer"
  51. Select the modeled form [TestFormA]
  52. Select a section of the form in the "Sections" field and click [Show Section]
  53. Either make a change in the section and submit the form or just submit the form without any changes
  54. Validate the form submits successfully (Note the current date and time)
  55. Repeat step 2
  56. Validate results are as expected
  57. Open form "Form Deletion"
  58. Select modeled form [TestFormB]
  59. Populate the required fields and submit the form
  60. Validate submission is successful. (Note the current date and time)
  61. Repeat step 2
  62. Validate results are as expected
  63. Open form "Table Deletion"
  64. Select modeled table [TestTableB]
  65. Populate the required fields and submit the form
  66. Validate submission is successful. (Note the current date and time)
  67. Repeat step 2
  68. Validate results are as expected
  69. Open form "Envelope Import"
  70. Click "Select Envelope"
  71. Navigate to location of the export file saved for [TestEnvelopeB]
  72. Select to import the envelope as an "Overwrite"
  73. Submit the form
  74. Validate submission is successful. (Note the current date and time)
  75. Repeat step 2
  76. Validate results are as expected
  77. Open form "Form Definition" again
  78. Select the form [TestForm]
  79. Go to the "Object Def" section and add a "Report" object
  80. In the "Report" field select report [ImportReport] imported in the set up
  81. Submit the form
  82. Open form 'Import Reports
  83. Click "Update Existing Report"
  84. Select the report [ImportReport] imported in the setup
  85. Click [Select Report for Import] and select a new report
  86. Submit the form (Note the current date and time)
  87. Repeat step 2
  88. Validate results are as expected
  89. Open form 'Caseload Type Definition' to define a new modeled caseload type
  90. Submit the form
  91. Open form 'Table Definition'
  92. Select [TestTable]
  93. Add a column to the table using the caseload type just created in the previous step
  94. Submit the form
  95. Return to 'Caseload Type Definition'
  96. Select the caseload type just added in step 15 any change any field on the form.
  97. Submit the form (Note the current date and time)
  98. Repeat step 2
  99. Validate results are as expected
  100. Open form 'Notification Type Definition' to define a notification type.
  101. Submit the form
  102. Open form 'Table Definition'
  103. Select [TestTable]
  104. Add a column to the table using the "Notification" type just created in the previous step
  105. Submit the form
  106. Return to 'Notification Type Definition'
  107. Select the notification type just added in step 28 any change any field on the form.
  108. Submit the form (Note the current date and time)
  109. Repeat step 2
  110. Validate results are as expected
  111. Open form 'Form Signature Authentication'
  112. Select [TestFormA]
  113. Set "Require Signature at Form Filing" to "Yes" and populated any require fields
  114. Submit the form
  115. Validate submission is successful. (Note the current date and time)
  116. Repeat step 2
  117. Validate results are as expected
  118. Open form 'Report Definition' to create a new report
  119. Select any report in the "Select Report" field
  120. Set 'Associate Report with Modeling Envelopes' to 'Yes' and select [TestEnvelopeA] in the "Envelopes" field
  121. Populate any other required fields
  122. Submit the form (Note the current date and time).
  123. Repeat step 2
  124. Validate results are as expected
  125. Open form "Report Definition Export"
  126. Export the report definition created in previous step
  127. Open form "Report Definition Import"
  128. Import the report definition exported in the previous step as an "Overwrite"
  129. Submit the form (Note the current date and time)
  130. Repeat step 2
  131. Validate results are as expected
  132. Open form 'Dictionary Update'
  133. Select the dictionary field used in form [TestFormA]
  134. Make a change to field, for example the dictionary description
  135. Submit the form (Note the current date and time)
  136. Repeat step 2
  137. Validate results are as expected.
  138. Open form "Dictionary Export"
  139. Select the dictionary field modified in the previous step and export the file
  140. Open form "Dictionary Import"
  141. In the "Select file" field, select the file just exported in the previous step
  142. Submit the form (Note the current date and time)
  143. Repeat step 2
  144. Validate results are as expected. It will record that the envelopes were modified by 'Dictionary Import'
Topics
• Modeling • NX • SQL Data Access
Table Changes

Table Column Change
SYSTEM.RADplus_envelope_info data_entry_by New
SYSTEM.RADplus_envelope_info data_entry_by_option New
SYSTEM.RADplus_envelope_info data_entry_user_id New
SYSTEM.RADplus_envelope_info data_entry_user_name New
SYSTEM.RADplus_envelope_info data_entry_option New
SYSTEM.RADplus_envelope_info data_entry_option_desc New
SYSTEM.RADplus_envelope_info data_entry_source New
SYSTEM.RADplus_envelope_info data_entry_date New
SYSTEM.RADplus_envelope_info data_entry_time New
SYSTEM.RADplus_envelope_info data_entry_utc New
SYSTEM.RADplus_envelope_info data_entry_timezone_info_all New
SYSTEM.RADplus_envelope_info data_entry_time_j New
SYSTEM.RADplus_envelope_info data_entry_offset New
SYSTEM.RADplus_envelope_info data_entry_timezone_short New

 

  • Was this article helpful?