  Importing case type records using extension points
|
|
You can use the following extension point activities to automatically import rules and data records from built-on applications when you add case types using Application Express, or when you use the Add or Import (case type) commands in the Cases Explorer.
- Rule-Obj-CaseType.pyPrepareFrameworkAssetsForGeneration — Prepares a list of assets for generation; called for each case type that is generated.
- @baseclass.pyPrepareFrameworkAssetsForGenerationSetup — Runs before pyPrepareFrameworkAssetsForGeneration; sets up pages that will need to be generated and copied to
GenerationQPage.
- @baseclass.pyPrepareFrameworkAssetsForGenerationPost — Runs after pyPrepareFrameworkAssetsForGeneration; adds pages that pyPrepareFrameworkAssetsForGenerationSetup created, and that pyPrepareFrameworkAssetsForGeneration augmented on
GenerationQPage.
Notes:
- The extension points create pages for the assets and add them to a list. The extensions should not save or commit records to the database as the calling processes handle those tasks.
- The extension points are called from PegaAccel-Task-ApplicationProfile.pzPrepareFrameworkAssetsForGeneration in Application Express, and from Rule-Obj-Class.pzCreateCaseType in the Cases Explorer.
- Set when rule @baseclass.pyIsFrameworkAssetGenerationForCasesEnabled to
true to enable these extension points. The default setting is false
