Source - Objects

Modified on Fri, 13 Oct 2023 at 09:39 PM

As previously described a Business Object represents all the data flowing through the migration related to one specific item in the business being migrated. 

Examples of Business Objects, of course, depend on the nature of the business but could be Customers, Account, Policy, Patent, Mortgage etc.

On the Source/Objects panel, we see the objects for this particular project displayed.

The meaning of the columns are:

The Object is shown as a parent with one or more children.
The count of Business Object instances in the staging tables (as defined by the Discriminator on the Card Business Object in the Source Map)
The number of Business Object instances dropped during the Export. The Business Object is dropped if a Severity Drop is assigned to a raised Flag when exporting a Business Object
The number of Business Object instances that where Rejected during the Export by firing an Event with Severity Reject Root
The number of Business Object instances that where Exported successfully
Any difference between Source and the sum of Dropped, Rejected and Exported. Any difference indicates that not all Business Object instances have been processed

As mentioned previously the State (green dot) represents that this migration has passed testing.

There are no dependencies in the export of Business Objects.

Click the Export button to show the Business Object Selection dialog:

This will prompt this screen.

The Business Object Selection Dialog

With minor differences the Business Object Selection dialog is used to submit jobs several places in the Portal Operations interface. Let's have a quick look at it:

Available / Selected
Move Business Objects to the Selected box to include in the job(s) being submitted.
If you know the key of a given instance of a Business Object, you can supply it here to process only this instance. The key is subject to an Sql like query and should at a minimum be pre- and suffixed with the Sql wildcard %.
Choose what to include:
  • All: All instances
  • Rejects: Only Rejected instances
  • Difference: Any instances in the Differences column
Wait for Debug
If checked, the job will be submitted but immediately pause until a debugger is attached. Allows you to debug your manual rule implementations.
Type a number to limit the instances processed by the job.
Fast Track
Only available when exporting. For each instance, the Portal Operations runtime will:
  • Execute the Source Engine
  • Execute the Target Engine immediately,
  • Only store the Target result. Unless the instance is Rejected, then everything is stored as normal
Profiling Level
The generated code is instrumented and in addition, migFx provides you with the possibility to instrument manual rule implementations. If a Profiling Level other than None is chosen, this instrumentation is activated and will log elapsed time in the execution tree. Useful to locate potential bottlenecks if the migration is suddenly performing badly.

All you have to do is check that the Card Business Object is the only one in the Selected box and click the Submit button to submit the job.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article