Your Modeler workspace contains a structure built by the Modeler CLI that holds the
contracts and other artifacts. The workspace also contains other local configuration data that
are required for the workspace or for generating output of the VS Code based Modeler build
processes.
Required Editions
Available in: Enterprise, Performance, and Unlimited
Editions that have Consumer Goods Cloud enabled
When you create a Modeler workspace, here’s the high-level structure and contents of the
Modeler workspace:
appl: This is the application folder.
build: The application build folder contains generator and validator results. This
folder also stores the deployment.zip created by the generator when you run the
package command.
app: This folder contains the clockwork, externalFiles, and replicationFiles
directories.
localeSnippets
config: This is the application configuration folder.
config.json: This file contains the settings for both simulator and framework.
For example, salesforce connection data, the unique ID of your Modeler workspace,
and the simulator port.
data: The application data folder contains runtime information.
branch.config.json: This file contains configuration settings to manage and customize
the behavior of individual branches within a project. This configuration is applicable for
a branch.
USE_LATEST_XSD_VALIDATIONS - Configure the
auto-completion capability in combination with the XML Language Support extension by
Red Hat. This setting determines the XSD validations to use when the generator builds
or validates contracts and the XSD files to link to the contract types in the
$workspace/.vscode/settings.json file. Set the setting to
true to enable the dynamic proposal of keywords
during contract customization. Default is false.
contractSnippets: This folder contains the templates for commonly used contracts such as
business object (BO), datasource (DS), list object(LO), lookup object (LU), print layout
(PL), process (PR), UI, and ComplexPricing business logic files. You can easily copy and
adapt the template contracts in this directory for customization purposes.
src: This is the source folder that contains the contract files. As part of the initial
set up, extract the core contract files from the Modeler Design Contract zip to this
folder. Subsequently, pull or fetch the contracts from the repository that you have set
up, such as Git.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.