std.CPRenditionChanged
This job signals to the server that a property of a DMS object’s rendition has changed. Typically called by the rendition service whenever it has freshly produced, updated or discarded a rendition or one of its aspects.
The job returns no data; instead — depending on the supplied Reason — it triggers
server-side follow-up actions:
-
Update of the indexing status in
osftslog(columnflag2, see value rangeflag2). -
Creation of a follow-up message in
oscpmqueue— typically a message in theFULLTEXTDOCqueue so the full-text indexer reprocesses the object with the updated content. -
Update of the page count in the object metadata (when
Reason = PAGECOUNT).
The complete CP lifecycle is described under Capture and Processing Messages (CP).
|
This job is not listed in the official enaio® standard engine overview ( |
1. Input Parameters
| Name | Type | Required | Description |
|---|---|---|---|
|
INT |
Yes |
Numeric ID of the DMS object whose rendition has changed. |
|
INT |
Yes |
Object type ID of the DMS object. |
|
STRING |
Yes |
Kind of rendition change. Known values: see Values for |
|
STRING |
Yes |
Identifier of the reporting service instance (typically: |
|
INT |
Yes |
Reserved; always pass |
|
INT |
No |
|
1.1. Values for Reason
| Value | Meaning |
|---|---|
|
The extractable full-text content of the object has changed (new OCR extraction or text
layer from a PDF/Office document). Triggers a re-indexing via a new |
|
The page count of the rendition has been (re-)determined — either because the document was converted for the first time or because the conversion yielded a different page count. Primarily updates the stored page count; a re-indexing is only triggered if indexing depends on the page count. |
|
A slide representation (preview image / per-page images for quick display) has been produced or changed. Affects mainly the display cache and typically does not trigger a re-indexing. |
3. Notes
-
Asynchronous in effect: the call returns immediately after the status changes and messages have been queued. The actual re-indexing happens later when the full-text indexer picks up the new message.
-
No caller-side deduplication: multiple calls with the same
(ObjectID, Reason)insert a new message inoscpmqueueeach time. The implicit collapse happens only on pickup — see Coalescing of redundant messages. -
The job is intended for internal service contexts (technical user) and performs no content-level permission check.
4. Related Jobs
-
std.GetNextCPMessage — picks up the follow-up messages created by this job (e.g. from the
FULLTEXTDOCqueue) -
std.GetCPObjectIdxFulltext — called by the full-text indexer after the pickup to read the updated full-text content
-
std.DispatchCPMessage — acknowledges the follow-up message after processing
-
std.CreateCPMessages — more generic variant for creating CP messages without
osftslogstatus update -
cnv.GetRendition — produces a rendition for a document