Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML DA: How to reference component version properties within process steps
DA: How to reference component version properties within process steps
CMS-XML Request plug-in process step to set value of component version property from process step
Request plug-in process step to set value of component version property from process step
CMS-XML DA: An overview of event driven import of component versions
"version": "value" NOTES: If you wish DA to consider all existing versions for import, provide only the " component " line in the JSON array (i.e., omit the " properties "). If you wish to import more than one version, repeat the "version" line with a comma separating each new line from the previous.
CMS-XML SDA: Component process property does not display related component
Add a new property to a component process. When running an application process that calls this component process (for several components ) you are unable to see which component and version the property is applicable to.
CMS-XML SDA: serenara-client importVersion requires property named baseline for components of source type Dimensions
The online help indicates that a json file of the following form is required to import a version using the serenara-client command line:{ "component": "Component name/ID", "properties": {
CMS-XML Secure property value lost on Copy Component during import
Create component with any SCT which has secure field (e.g. CM SCT with "Password" field) Configure SCT to be able to import versions Click to copy component from Management->Components
CMS-XML SRA: How to define a property value that will be set at request time but readable by the component process.
1. create a component 2. create the component process (e.g. operational w/o version to simplify) 3. at the tab Properties of component process create property comp_proc_prop and define its value
CMS-XML SRA: application/component JSON import fails for some cases where secure property values are used
component process called prc_cmp_paul of type operation (no version needed) In the component process, add a shell step to run – echo Hello World In the component process create a property called PAULS_PROP with a type of SECURE Add the component to the application Create an application process called prc_app_paul In the application process add a step to “apply configuration”
CMS-XML RLM 5.1: How to see the Turnover, Component, and Component Versions deployed to a specific environment (SBM Advanced XML Report)
On the state form called "Base State Form", add a tab to the bottom (or use the existing History tab). Drag and drop an Embedded Report widget on the chosen tab. On the Properties > General tab, click on Configure Report.
CMS-XML SDA: Error "This version cannot be deleted because it is in use by the following" when deleting component version history
Pipeline execution requests Process request property contexts Process request property sheets
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs