C1000-004 Sample Questions & Answers

The Cúram wizard framework provides a built-in state management mechanism. It automatically serializes the page data into a WIZARD_STATE page parameter, which is passed from one page to the next. Developers can access and modify this state object on each page of the wizard. This is the standard, compliant, and most efficient method, avoiding direct session manipulation or custom database tables for temporary wizard data.

A Deferred Process is the ideal solution for this scenario. It allows the main transaction (creating the evidence) to complete quickly and return control to the user, while the potentially long-running task (sending the email) is handled asynchronously in the background. The evidence creation logic would enqueue the deferred process, which then executes in a separate transaction. A standard method call would be synchronous and block the UI. A batch job is for scheduled, bulk processing, not immediate, event-driven tasks. A custom event could be used to trigger the deferred process, but the deferred process itself is the mechanism for the asynchronous execution.

The Application.prx file is the central location for defining application-wide properties, including localization settings like date and number formats. By setting the curam.environment.default.dateformat property in this file, a developer can enforce a consistent date format across the entire application for a specific locale. Modifying individual UIM files is inefficient, CSS cannot control date formatting logic, and messages.xml is for translatable text strings, not formatting rules.

The correct way to model a database index in Cúram is to create an Index association. This is a UML association stereotyped as > that typically originates from and targets the same entity. In the properties of this association, the developer specifies which attributes of the entity are part of the index. The Cúram generator will then create the corresponding DDL for a unique or non-unique index during the database build. The other options do not result in the creation of a database index.

A Façade class is the ideal choice for this purpose. The Façade design pattern in Cúram is intended to provide a simplified, high-level interface to a complex subsystem. It is the standard place to aggregate calls to multiple Process or Entity objects to construct a data transfer object (DTO) or, in this case, the JSON response for a REST API. This keeps the JAX-RS resource class clean and focused on HTTP concerns, while the Façade handles the complex business logic.

The compliant approach for customizing artifacts like .nav files, especially after an upgrade, is to take the new version of the OOTB file, copy it to your custom component directory (maintaining the same folder structure), and then re-apply your specific customizations to this new copy. This ensures that all the new structural changes and features from the upgraded version are preserved, and your custom logic is correctly integrated. Simply overwriting the file or editing the OOTB file directly are non-compliant actions that will cause issues and be lost on subsequent builds or upgrades.

When the build database target runs, the Cúram generator creates the DDL scripts based on the UML models and places them in the EJBServer/build/svr/gen/ddl directory. This is the primary location for developers to find and inspect the SQL scripts that define the database schema, which is essential for troubleshooting database build failures.

The checkOperation stereotype is a special entity operation designed for this exact purpose. It is invoked by the Cúram infrastructure before any read, modify, or remove operation on an entity instance. By implementing checkOperation, a developer can add logic to inspect the record's status and throw an exception if the status is 'CANCELLED', effectively preventing the operation from proceeding. This provides a centralized and secure way to enforce the soft-delete business rule.

The best practice is to perform data calculations and transformations on the server side. The façade method, which prepares data for the UI, is the perfect place for this. The method should be modified to iterate through the list of clients, calculate the age for each one, and populate a new 'age' attribute in the list struct that is returned to the UIM page. The UIM page then simply displays this pre-calculated value. This keeps business logic on the server, ensures consistency, and is more performant than client-side calculations, especially for large lists.

The IBM Cúram SPM platform includes a standard, out-of-the-box (OOTB) Attachments framework specifically designed for managing documents and other files related to cases and participants. This framework handles the storage, retrieval, and security of attachments in a compliant and integrated manner. Using this feature is the best practice, as it avoids the need to build a complex and potentially non-compliant custom solution.