What Rules Are Automatically Generated?

When you import a high-fidelity Blueprint, the system performs a substantial amount of rule authoring for you. The following are key Rule Types and artifacts created:

Rules Details
Case Type Rules
  • Workflow Stages and Steps: Each stage and step defined in the Blueprint is translated into workflow Rules, including alternate stages (for example, for approval rejection).
  • Step Views: For every 'Collect Information' and 'Approval' step, the import creates corresponding view Rules, ensuring that the runtime UI matches the Blueprint design.
  • Case Data Model: All fields, including those marked as primary, are implemented as properties in the case class. Data references are set up to link to related data objects.
  • Assignment Routing: Based on Blueprint routing settings.
Data Object Rules
  • Data Classes: Each data object becomes a class with its own property definitions.
  • Primary Field Highlighting: Properties marked as primaryare configured to appear in summary panes and highlighted views.
  • System of Record Integration: Data objects are linked to their designated system of record, whether internal or external.
Persona and Access Control Rules
  • Access Groups and Roles: For each persona, the import creates access groups and persona-specific access roles, configuring permissions as specified in the Blueprint.
  • Channel Configuration: Portal Rules are generated to match the channels (web, mobile, email) assigned to each persona.
  • Workbaskets/Work Queues: defined for the personas that are selected for routing in the Blueprint.
Sample Data and Records Management
  • Sample Records: The import process generates realistic sample data for each data object, not just placeholders, enabling immediate testing and validation.
  • Records Manager Landing Page: A records manager is set up in the work portal, allowing users to inspect and manage data objects in line with access policies.
User Stories
  • Implementation Tasks: Components from the Blueprint design (for example, workflow steps, data fields) are automatically converted into Tasks on the Implementation Planner Board, providing a ready-made backlog for implementation and refinement.

How Import Fills Blueprint Gaps

The import process is designed to be 'smart' and resilient, filling in gaps where the Blueprint may be incomplete or ambiguous:

  • Default Behaviors: If a workflow step lacks a defined view, the import creates a default view based on the data model.
  • Alternate Stages: The system recognizes patterns (for example, approval steps) and automatically adds alternate stages for common scenarios like rejection, even if not explicitly specified.
  • Data References: When a field is marked as a data reference but the target object is missing, the import attempts to create a placeholder or link to an existing object if available.
  • Access Controls: If persona permissions are underspecified, the import applies sensible defaults based on best practices, ensuring no persona is left without basic access.
  • Naming Conventions: Where naming is absent, the import applies standard conventions to maintain consistency and avoid conflicts.

Shortfalls and Manual Steps:

The Blueprint import process automates several aspects of application construction; however, certain types of complex logic, integrations, and custom configurations are not included in the Blueprint and must be configured manually to complete the solution.
  • Complex Logic: Advanced business logic, integrations, or custom UI configurations not captured in the Blueprint must be manually implemented post-import.
  • Synchronization: If you select Use Existing for assets, changes in the Blueprint (for example, new properties, updated permissions), are not automatically synchronized and manual updates are required.
  • Embedded Data: While embedded data structures are increasingly supported, some advanced scenarios (for example, deeply nested references, custom views) may require manual refinement.

Summary Table: What Gets Built Automatically

Artifact Type Created Automatically Manual Refinement Needed
Case Types ✔ Workflow, Data Model, Views Advanced logic, custom UI
Data Objects ✔ Classes, Properties, Sample Data Complex integrations
Personas ✔ Access Groups, Roles, Channels Custom permissions
Access Controls ✔ Basic permissions, portal setup Fine-tuning, exceptions
User Stories ✔ From Blueprint components Backlog refinement
Embedded Data ✔ Basic support, reusable views Deep nesting, advanced scenarios
Routing ✔ Work Baskets Create an access role and assign it to the work basket for security.
NOTE: This summary reflects typical manual refinements and does not represent the latest Blueprint or import capabilities; details are subject to change.