Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Cloud Service Automation4.90

Use > OO Designer > Author in OO Designer > Author Flows > YAML File Textual Representation

YAML File Textual Representation

You can view the YAML file corresponding to a selected flow, operation, decision, or system property, by clicking the Show as Text button in the Authoring pane toolbar.

The YAML file includes the textual representation of the UI editor, so that each action done in the UI editor, such as, for example, adding inputs, editing outputs, adding steps, is reflected in the YAML file.

It is not recommend to set a default constant value when an input and output is marked as sensitive. The values are displayed as asterisks in the file.

Example of a typical file:

The first part (in green) displays the contents of the description of the item (flow, operation, decision, system property), as well as the description of input, output, and result.

#!!
#! @description: This flow does something.
#! @input flow_input_0: This input is for something...
#! @output flow_output_0: This output is for something...
#!!#

The second part (in blue), starting with namespace:, provides the CloudSland code that corresponds to the information about the selected flow or system property that were entered in the UI editor.

namespace: sss
flow:
  name: flow1
  inputs:
    - flow_input_0: "${get_sp('io.cloudslang.base.from')}"
    - flow_input_1: "${get_sp('io.cloudslang.base.hostname')}"
  workflow:
    - get_time:
        do:
          io.cloudslang.base.datetime.get_time: []
        navigate:
          - FAILURE: CUSTOM
          - SUCCESS: SUCCESS
  outputs:
    - flow_output_0
  results:
    - SUCCESS
    - CUSTOM

The third part (in blue), starting with extensions: provides the CloudSlang code that enables the graphical representation of the flow in the Graph tab. At run time, this section is ignored.

extensions:
  graph:
    steps:
      get_time:
        x: 64
        y: 132
        navigate:
          dd888147-9fbf-25ef-bee5-d9946ce91bef:
            targetId: 519f1a15-eeb9-65f8-c115-bb0d96faff02
            port: SUCCESS
          56ba3221-c9f9-6dc5-689a-ffbd26643467:
            targetId: 54582fee-d5e9-315e-149a-5c2a884c0297
            port: FAILURE
    results:
      SUCCESS:
        519f1a15-eeb9-65f8-c115-bb0d96faff02:
          x: 384
          y: 75
      CUSTOM:
        54582fee-d5e9-315e-149a-5c2a884c0297:
          x: 360
          y: 230

Send Help Center feedback