Previous Topic: Upload a Model to the EncyclopediaNext Topic: Automatically Applying a Model to the Parent Model


Applying a Model or Subset to the Encyclopedia

Apply processing updates the parent model with changes made to a child model.

A child model is a model that is created during extract processing. You can extract the entire model from the parent model to create one child model, or extract multiple discrete subsets from a single parent model to create multiple child models.

Changes can be made to a child model after checkout to a workstation using the toolset or, directly on the CSE through the Construction Client or the Encyclopedia Client. Changes that are made to a model using the toolset include adding, modifying, and deleting model objects, take effect at checkin. Changes that are made to a model through the Construction Client are related to packaging, member name modification, and environment or configuration parameters. Changes that are made to a model through the Encyclopedia Client are related to object rename and object delete operations.

Changes to the child model can be applied to the parent with and without checkin. The option that you use affects the status of the child model. When you apply the Without Checkin option, the child model status is modifiable. When you apply the With Checkin option, the child model status is read-only.

When a child model or its subsets are checked out and you update the child model with the Update But Do Not Checkin option, the parent model must be updated with the Apply Without Checkin option. The Apply With Checkin option can only be used after the child model or all of its subsets are checked back in.

When you use the Apply Without Checkin option, the child model's status is Update But Do Not Checkin. When you use the Apply With Checkin option, the child model's status is Update and Checkin Model.

Update procedures are site-determined and vary with the business needs. Possible scenarios include:

Note: We recommend that you apply options to keep the parent model synchronized with the child model.

Apply processing has three steps and each step creates a file:

  1. Identifies all changes that are made to the child model and creates the apply.trn file.
  2. Applies the changes to the parent model and creates the everify.trn file.
  3. Verifies apply succeeded and creates the everify.rpt file.

Use Apply And Checkin to apply changes to the parent model and checkin the child model after changing it.

Use Apply But Do Not Checkin during development when you want to apply completed changes to the parent model and keep the child model checked out.

Use Resend Apply to continue the apply processing when a communications failure occurred between creating apply.trn and step 2 completes.

Use Verify Apply to determine if apply succeeded when a communications failure occurred between creating everify.trn and step 3 completes.

When a communication failure interrupts the Apply And Check In command or the Apply But Do Not Check In command, check the user ID subdirectory in the CSE directory for the APPLY.TRN and EVERIFY.TRN. You re-issue the Apply command that is based on the existence of either, both, or neither of these files:

The method that you use to apply changes depends on where the parent model resides.