Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This will show you all available property.* pipeline commands and their description in the terminal.

Another possibility (only:

Status
colourBlue
titleENTERPRISE
,
Status
colourPurple
titleCORPORATE
) to see the documentation of available commands is to go to this url:

...

This will list all available commands to manage properties in the property store. Click on such a command to get details about it or to execute it online.

If you want to manage the property store from your local command line, you can call any of these commands also using the CLI:

Code Block
pi command COMMAND_NAME PARAM1=VALUE1 PARAM2=VALUE2

See Command Line Interface (CLI) for more details about using the CLI.

Create a new property

To create a new property, you need to use the command property.schema.put.

...

See this link of your instance for details about this command (replace NAMESPACE by your real namespaceonly:

Status
colourBlue
titleENTERPRISE
,
Status
colourPurple
titleCORPORATE
):
https://portal-NAMESPACE.pipeforce.net/#/pipeform?pipe=property.schema.put

...

Note: The property must already exist before you set its value using. So use property.schema.put to define the property and then property.put to set its value.

...

See this link of your instance for details about this command (replace NAMESPACE by your real namespaceonly:

Status
colourBlue
titleENTERPRISE
,
Status
colourPurple
titleCORPORATE
):
https://portal-NAMESPACE.pipeforce.net/#/pipeform?pipe=property.put

...

Info

Why are there two different commands to create a property and set its value?
Because there are two different security levels with permissions. Those users who are able to change the value of a property with property.put not always have the permission to create a new property using property.schema.put. Having two commands allows it to differentiate in a pipeline what a user can do since in PIEPFORCE PIPEFORCE any command can have assigned different permissions.

...

See this link of your instance for details about this command (replace NAMESPACE by your real namespaceonly:

Status
colourBlue
titleENTERPRISE
,
Status
colourPurple
titleCORPORATE
):
https://portal-NAMESPACE.pipeforce.net/#/pipeform?pipe=property.schema.delete

...

See here how to setup such a customization workspace: Local Low-Code Workspace

See here for a getting started guide how to setup the CLI and use the local workspace: https://logabit.atlassian.netnull/pages/createpage.action?spaceKey=DEVEX&title=Getting%20Started%20-%20Basics&linkCreation=true&fromPageId=988807265 .

Working with Visual Studio Code

...