A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Cache consumer
A job that fetches data from the cache if it is available (in other words, it "consumes" the cache) . If the cached result is not available, the consumer executes the job and retrieves the actual job result.
Cache producer
A job that populates cache with data (in other words, it "produces" the cache).
Choose step
A step of type "Choose step" lets you define the conditions under which other job steps should be executed. Choose steps have the following structure:
When {some expression}
Execute (some step)
Otherwise
Execute (some other step)
Under each "Choose step", you can nest other Choose steps (sub-conditions), for example:
When {expression}
When {expression}
Execute (step)
Otherwise
Execute (step)
Otherwise
Execute (step)
Any number of conditional steps can be defined.
Within any When / Otherwise pair, FlowForce Server executes only the condition that is true; the other condition is ignored.
Container
As the name of the term implies, a container is data packaged together. In FlowForce Server, containers can be roughly compared to folders on an operating system. Containers can contain any of the following: jobs, credentials, functions, and other containers. By setting permissions on containers, you can control who can view or access the data inside them. Organizing data into containers and setting up the relevant permissions for each container is a good security practice.
Credentials
A credential object stores authentication information. This is typically the combination of user name and password associated with a user account on the operating system where the FlowForce Server job runs, but it can also be a set of HTTP or FTP credentials.
