Content builder
The value resolvers in this category read, write, delete or create content of different types using different methods:
|
Value resolver |
Purpose |
Reference |
Return value |
|
The contents of 'attached' Documents (with reference to the entity in the input value) are read as a list of 'content' objects. |
'Content' object |
||
|
Delete a file in the file system of the Lobster Data Platform / Orchestration server or read or write its content (as text or 'content' object). |
|||
|
Create a print document with the data of one or more entities in the input value.
|
|||
|
Create a text (plain text or e.g. also HTML or any other text-based format) by interpreting the data in the 'print XML' (Print object) for the current context (reference object(s), session data, variables) using a RAW template.. |
|
Text |
|
|
Create a text that reflects the server XML created via the ExportManager for the entity in the input value. |
|
||
|
Provide the return value of a Lobster_data profile. Depending on the parameterisation of the value resolver, the result is either a 'content' object, a text or an entity parsed from the XML response of the profile. |
'Content' object or text or entity |
||
'Content' object (Content)
Some of the value resolvers in this category refer in the return value to the 'content' object (de.lobster.scm.actionevent.actor.content.Content) with the following data structure:
|
Field |
Data type |
Content |
Example |
body |
byte[] |
base64 encoded content |
JVBERi0xLjcNCiW1... |
mediaType |
String |
MIME type of data in the body field |
application/pdf |
name |
String |
File name |
po234711.pdf |
Lobster Data Platform / Orchestration uses different classes with reference to file contents. The following table shows which fields correspond to the fields of the 'content' object in each case: