Add a configured field and prepare its delivery
Create a persistent custom attribute, place it with Page Designer, test saved values, and move the configuration with an ACP.
CRIM code library
CRIM means Configurations, Reports, Integrations, and Modifications. Start with a worked problem in each category: follow the numbered actions, adapt the example to your environment, and check the result before delivery.
Reference baseline: IFS Cloud 26R1. These are source-informed or documentation-based drafts, not environment-verified procedures. Example component and business-object names are fictional; adapt them to your target and generate with matching tools.
Choose a worked example
Section titled “Choose a worked example”| Category | Step-by-step problem | What you will check |
|---|---|---|
| Configurations | Add a persistent field with Entity Configuration and Page Designer | Save/reopen the value, publish the page, and deliver an ACP to another environment |
| Reports | Add a reference to a customer-owned operational report | Query and model → generated XML/XSD → bound RDL layout → registered PDF output |
| Integrations | Build and call a projection function | Generated service stub, original PL/SQL example, API discovery, authentication, and allowed/denied calls |
| Modifications | Add a Cust-layer persistent field | Entity storage, projection exposure, client placement, generation, and regression checks |
The examples share the fictional value DEMO-HO-014. They demonstrate four different kinds of change; they do not depend on one another or create a single ready-to-install solution. Each guide includes prerequisites, expected results, troubleshooting, an exercise with a solution, and cleanup.
Find a recipe by category or file
Section titled “Find a recipe by category or file”4 recipes
Connect a projection function to its implementation
Build a reference-normalizing projection function, implement the generated service stub, grant access, and call it through its actual API contract.
Add a persistent modification field
Trace an entity attribute through a Cust projection and client, with file roles, snippets, generation order, and validation.
Add a value to your own operational report
Add a report attribute with a synthetic SQL example, regenerate the schema, bind an RDL layout, and check the delivered PDF.
No recipes match those filters. Try a broader term or reset the filters.
Download the example materials
Section titled “Download the example materials”- Target and delivery worksheet — map the fictional names to real objects and record release, roles, delivery, and recovery.
- Acceptance checks CSV — fill in actual results for all four categories on development and target environments.
- Reference cases JSON and Oracle expression checks — seven inputs for the integration example; Oracle/IFS execution remains unverified.
- Report SQL fixture and illustrative XML — synthetic data for explaining the report pipeline, not an importable report package.
Continue within each category
Section titled “Continue within each category”After the worked example, use configuration lessons, reporting guides, integration tutorials, and testing and delivery lessons for related tasks. The four CRIM recipes are starting points, not a claim to cover every possible change.
Development practices
Section titled “Development practices”Use the development and modifications guides alongside the recipes. Work through naming and layering, optional components, entity security and time zones, SQL and PL/SQL performance, secure server methods, concurrency, and upgrade scripts. Each guide adds examples and checks for a specific engineering decision.
Workflows
Section titled “Workflows”The dedicated workflow learning center covers BPA triggers, variables, API and REST tasks, user forms, asynchronous execution, grants, delivery, and troubleshooting.
Start with a field
Section titled “Start with a field”For a source customization, follow Add a persistent modification field. For a runtime configuration, start with Add a configured field.
The file responsibility map explains authored versus generated files. The library currently covers four focused workflows; it is not an exhaustive CRIM reference.
How to use a recipe
Section titled “How to use a recipe”- Confirm the requirement and whether configuration already supports it.
- Trace the actual entity, service, page, and fragments in your target release.
- Adapt the example and inspect the generated result.
- Test behavior and permissions in a development environment before delivery.
All public snippets are original generic examples. Source traces are retained privately for editorial review.