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' ( |
| Text | |
Create a text that reflects the server XML created via the |
| ||
Provide the return value of a Lobster_data profile. Depending on the parameterization 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 |
|---|---|---|---|
|
| base64 encoded content |
|
|
| MIME type of data in the |
|
|
| 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:
Object →└ Field ↓ | 'Content' object | 'File information' object (see File form element) | 'Document' object (see Documents) | (see Custom type definitions) |
|---|---|---|---|---|
Content |
|
| 'Document content' |
|
Type |
|
| 'Type' |
|
Name |
|
| 'Name' |
|


