“Saving and loading Workflow Templates”.This section contains the following topics: Notifications can then be sent by the administrator with the configuration file, template files, and instructions on where to store the files. Tip: Default templates can be shared with others by having an administrator set up the template preferences file default_templates.binconfig, located in C:\Users\\AppData\Roaming\Certara\Phoenix\Configuration to point to a common location where the shared templates will be stored. Note: When a Workflow Template is imported into a workflow, it is necessary to remap any external data sources to objects in the Workflow Template. Workflow Templates can be imported into a workflow, although Workflow Templates do not save any datasets or data mappings. This allows a common analysis to be predefined for automated performance of repetitive analyses. What are the benefits of a Workflow Template?Ī workflow can be saved as a Workflow Template, in order to reapply an analysis on new data. Workflow Templates save the setup information for workflow and operational objects, and any pointers to an operational object’s results data. Project files save all parts of the project: all the datasets, code, rule sets, other information objects, and all workflows and operational objects. How are Workflow Templates different from project files? Workflows and objects contain pointers to datasets, but templates do not. Workflow Templates do not store pointers to non-results data, such as imported worksheets. How are Workflow Templates different from workflows? They also save pointers to results data, such as a Final Parameters worksheet. Workflow templates save a workflow operational object, and all the operational objects it contains. Note: Workflow Template files do not contain any mappings or links to external data sources, which means templates do not have data mappings to external sources, or with any parameter settings in external scripts (e.g., used when connecting with third-party tools). Templates contain the specific configuration of each operational object in a workflow, but do not contain the original data input sources. Workflow Templates can be created to expedite future analysis for workflows that are created to perform complex or specific functions. (Note that older WinNonlin Template ( *.wnlt) files can still be loaded into Phoenix, but are no longer created by Phoenix.) Workflow Templates are files that contain the operational objects and settings used with a workflow. A Workflow Template in Phoenix works like a template in Microsoft Word, it allows users to recreate the same steps over and over, and gives users a form or fields that can be used to automatically recreate a workflow to use with a new dataset.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |