Forum

There is no automated way to skip a workflow step based on existence or non-existence of an object type in the CR – the example being COBOL program which requires the additional manual compile step. The only way to handle your requirement is to make the step to compile the COBOL program an optional step that would be manually skipped by the developer if the CR does not contain a COBOL program. A simple way to communicate and document this situation is for the developer to note the COBOL compile requirement in the migration note.  It is also possible through the workflow API to write a custom method that interrogates the object list and triggers an email or pop-up message as a reminder if there is a COBOL in the list.  Contact support for more information on setting up the workflow API, if that seems like a useful option.

When an Export DMS is executed in Phire, the data file is captured in history, and can be used as the data file on a subsequent Import DMS.   The feature you’re looking for is provided as a button on the script history page.  So starting at the CR Script page, click the “History” hyperlink on the export Data Mover script.  This shows the script execution history where you will see a button like this:  .  Click that button and it will ask you to select the import script to associate with the data (this is a script that you would have written yourself to perform the import as you require).  Once you select the import script, you will see it added to the CR Script page as an Import DMS with the associated data file included.  The import is now ready to be executed either individually or as part of a migration.

If the assignment field on future tasks in the workflow are made display only, then this indicates that the current user does not have permission to reassign tasks.  That permission is granted here:  Phire Architect > Security Administration > Reassign Task Security.  The permission is granted to either a role or an individual user, similar to the other permission sin Phire.  And it can be granted to all task types, or specific task types depending on the requirements being met.