Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Adding data objects to organize data

Updated on November 15, 2021

Identify and manage the data that your Microjourney requires by creating data objects for your case types. When you ensure that users of your application have all of the information required to process business cases, you speed up case resolution and maximize work efficiency.

Adding data objects to your case life cycles creates draft relationships between the data and your business processes. By examining these draft relationships, you can optimize work by estimating what information a specific case requires and then planning how you can acquire this data. For example, if your case represents a hiring process that includes a Collect personal details stage, you can create draft data objects such as Address information and Insurance details. As a result, when building your application, you can clearly visualize the information that is essential to case resolution and clearly communicate the objective to your development team.

To provide complex solutions for your case types, you can also capture data from external systems. For example, in a hiring process, you can include a candidate's profile from an external web page.

What to do next: Plan and implement data objects in your application by completing the following tasks:

  • Associating data objects with case types

    Provide the transparency of data that a Microjourney requires by associating data objects with case types. When you define which data objects you need to create to process your business case, you improve the overall planning and development of your application.

  • Implementing draft data objects

    Provide data that is necessary to process your business cases and meet your goals by implementing draft data objects. When you plan your Microjourney, you can associate draft data objects with case types. By turning these data objects into permanent elements, you ensure that your customers can process the Microjourney successfully.

  • Associating attachment categories with case types

    To ensure that the workers who process your Microjourney have the relevant information, associate attachment categories with your case type. Visualizing the attachments required by your Microjourney helps you to gain a better overview of the information that your application users need to deliver. You can also communicate to your stakeholders what documents or other attachments are crucial in the Microjourney.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us