For those who have had the pleasure of using dspCompose, the Remediation Solution of DSP's tool set, it is quite apparent that the process from end to end requires a certain order in which to configure certain elements. For example, one cannot configure a data entry page without first generating objects for a template. There is, however, one feature in dspCompose that allows users a greater amount of flexibility when it comes to executing remediation as efficiently as possible.
Scenario
Suppose you have your template all configured and you have already activated it and added a request either manually, or had it created through some external means. Though before the remediation begins, the client comes back and asks for an additional role to be added so they can accommodate a new data manager. Since a request is already registered with the template and the template is active, a user cannot add another role. Even if the user tries to deactivate the template, the system will not allow it, because an active request is in the template. To solve this, the request would have to be removed and the template would have to be turned off. This course of action can be inefficient and frustrating. But does it have to be? No!
Developer Mode
If developer mode is enabled, a user can make changes to an active template with active requests. If disabled, no changes can be made to an active template with active requests. Simply navigate to Templates / Vertical View / Advanced tab / Developer Mode will be found towards the bottom. A few features to note:
-
Request deletion and template deactivation is not required to make changes to a template.
-
Allows for more rapid development.
-
Note that any modifications to an External Initiated Request or an ISA Request Scenario configuration is still not allowed.
BackOffice Associates offers professional, instructor-led training in an interactive, hands-on style. To view the latest schedule of classes currently offered, visit:
http://www.boaweb.com/company/product-training
Comments
1 comment