Page Comparison

System Area

Composition of Deliverable

Migration Recommendation

Deployment Estimate

Entity

Project team has added some fields to a core Aptify entity or subtype to support an object or wizard.

Use the Entity Packer to install the entity with additional fields on the target server, or if a subtype, install its parent entity. Alternatively, once approved in a review cycle by an Aptify-oriented DBA, manually create the fields to the entity in the target environment.

Minutes per entity
OR
<1 minute per field.

Entity

Project team has changed existing fields to a core Aptify entity or subtype to support an object or wizard, OR added or modified other entity attributes/properties.

Once approved in a review cycle by an Aptify-oriented DBA, manually update the fields or properties in the entity/subtype in the target environment.

<1 minute per field.

Entity

Project team has added a subtype to a core Aptify top-level entity.

Use the Entity Packer to install the subtype entity on the target server. Note: This is done by packing the top-level entity. All changes to the existing entity should be made following the rules above prior to completing this step.

Minutes per subtype.

Entity

Project team has developed some new entities (top-level and subtype) to support business functionality specific to the client.

Project team can use the Entity Packer to pack and unpack these entities on the target server. The entity packer will use the Data Packer functionality as part of the Entity Packer to also pull Process Pipelines and Form Templates associated with that entity without the project team needing to use the Data Packer specifically.

Minutes per entity.

Object Repository

Project team has written an Entity Plug-In or other .NET assembly that was created for the purpose of enforcing client-specific business rules.

Project team should open Aptify pointing their Startup.exe.config or attributes.xml file to the Target environment; upload this new object into the object repository from the development environment. Any entity changes should be deployed using the above rules.

<1 minute per object.

Object Repository

Project team modifies an existing Form Component, Process Component, Entity Bulk Operation Component, or Layout Control.

Upload the modified object to the Object Repository using a new name in a client-specific package. Then, update the metadata record for the specified component to point to the new version of the object.

< 1 minute per object.

Business Logic

Project team has developed a Process Pipeline to solve a business workflow need on an existing Entity.

Project team will use the Data Packer for the migration. They ONLY need to select the one Process Pipeline they intend to move. The Data packer will use its own logic how to find all process components and steps and every piece of data required to run the Process Pipeline on the target server. Event Handlers are not moved to prevent automatic availability of a Process Flow upon deployment. If an Event Handler is not present on a target server that is used with that Process Pipeline, the Event handler can be manually created on the target server. But no other individual items need to be selected at pack time in order for a process pipeline to be migrated.

Minutes per Process Flow.

Business Logic

Project team has developed an Entity Bulk Operation (EBO).

Project team should manually create the EBO in the target environment, copying and pasting with the Windows clipboard where re-keying would be cumbersome.

Minutes per EBO.

Business Logic

Project team has developed only a new Database Object defined as a Stored Procedure, View, Function, or Trigger that is being used in conjunction with a wizard, object, or other existing entity.

Project team should open Aptify pointing their Startup.exe.config or attributes.xml file to the Target environment, and then create a new Database record, specifying the object name, type, and SQL code (copied and pasted from the source server for that object).

Minutes per Database Object.

GUI

Project team has created or modified a Form Template for an entity, perhaps even developing a new Form Component object.

Project team will use the Data packer to pack ONLY the Form Templates that were configured. The Data Packer logic will recognize underlying dependent items such as Form Components and Form Template Parts. No other items need to be selected with the data packer to move these except selecting the Form Templates themselves. Entity changes should be modified using the above rules.

Minutes per Form Template.

GUI

Project team has created new Dashboards for Applications.

Project team will use the Data Packer to pack ONLY the dashboards that were created. The Data Packer logic will recognize underlying dependent items such as Dashboard Parts and Dashboard Components. No other items need to be selected with the Data Packer to move these except selecting the Dashboards themselves.

Minutes per Dashboard.

GUI

Project team has developed new Applications and attached various entities to these new Applications.

Project team should open Aptify, point it to the target server, and create the new Applications. Then, specify the Entities that should appear in that application on the Application's Entities tab.

Minutes per Application.

Reports

Project team has developed new Crystal Reports, Word Templates, Message Templates or other file based objects aside from compiled VB objects.

Project team should open Aptify, point it to the target server, and upload the items into the Object Repository directly and then attach them to entities where necessary on the Entities records.

Minutes per report.