Mapping eServer Solution Statuses to ATG Workflow Statuses

In eServer, each solution has a status that indicates its place in the publication process. ATG uses workflows and workflow statuses to record similar information. In ATG, the possible values for a solution’s status field are determined by the workflow that the solution belongs to – a solution’s status is not independent of its associated workflow, and the status is not user-editable. Instead, the status automatically updates as the solution moves through the workflow.

Therefore, an important part of the migration process is to select a workflow for each solution class you are migrating. You then create a mapping between the old solution statuses and the new workflow statuses. When a solution is migrated, its status is updated according to the map you create.

For more information on how ATG Knowledge uses workflows, see Using ATG Knowledge Workflows.

Note: When migration is complete, solutions have new workflow status values, but they are not actually placed into any workflow; no tasks are created for any migrated solutions. After migration, you should query for migrated solutions and manually create new projects for them as desired. For more information on workflows and Content Administration, see the ATG Content Administration Programming Guide.

You use the eserver_migration_config.xml file to map how your existing solution statuses correspond to new ATG workflow statuses.

For each solution class you are migrating, you create a solutionStatus tag in the XML file to specify workflow status information:

   <solutionClass tag="medical_solutions"
     workflowName="/Service/SvcPublishContent.wdl"
       <solutionStatus tag="status">
         <status old="wip" new="SvcDraft"/>
         <status old="review" new="SvcContentReview"/>
         <status old="verified" new="SvcStyleReview"/>
         <status old="pending_pub" new="SvcPublishedInternal"
         <status old="published" new="SvcPublishedExternal"
           autoDeploy="true"/>
         <status old="withdrawn" new="SvcDisabled"/>
       </solutionStatus>
   </solutionClass>

  • workflowName specifies the ATG workflow that solutions created in this solution class should use. The default value is /Service/SvcPublishContent.wdl. You can create new workflows for your solution classes, and use the workflowName attribute to specify your new workflow name. Different solution classes can use different workflows.

    Note: you can globally change the workflow that all solution classes use by changing the solutionWorkflowName property in the EserverMigrationService.
    properties     configuration file. If a solutionClass element contains a workflowName, this value will override any global setting in the EserverMigrationService.properties configuration file.

  • solutionStatus specifies the eServer property that ATG should recognize as the solution status field. Use the old and new attributes to map your old solution statuses to new workflow statuses.

  • autoDeploy identifies one or more of your solution statuses as the stage at which the solution is published. In the example above, the old published status meant that the solution was available to users. In the default ATG solution workflow, SvcPublishedExternal is the name of this status. Any solution whose status has autoDeploy=“true” will automatically be deployed to ATG Self Service when migration is complete. (You must have configured the publishing targets before deployment can happen.)

After migration, all migrated solutions are checked in to the Content Administration versioned repository. Next, an automatic quick deployment pushes solutions with status SvcPublishedExternal to the ATG Self Service server. You will need to index the solutions separately; see Running the Migration Module

 
loading table of contents...