2 Replies Latest reply on May 10, 2012 6:29 PM by user213133

    CSS Output Message Types

      We're syndicating spec data to an internal web service via CSS under 6.1. Specs are syndicated twice per GSM workflow to the same system, first as a "create" and then as an "update".

      So far in testing we haven't seen anything other than ADD types being output even when the same publication is syndicated more than once. The general GSM workflow steps are like this:

      1. Draft
      2. Developmental (Syndicate here as "create")
      3. Approved (Syndicate again here as "update")

      We would expect the message type at the Developmental step to be ADD, and then have a message type MODIFY at the Approved step to make it easier for the middleware program to know what it's looking at. But in both cases the XML comes out as an ADD in the syndicationCommand type attribute, and shows "Add" types in the catalog response section of the publication for both responses.

      I've tried using both the Initial Load and New publication types, but they both have the same results. The questions then, are:

      1. What triggers CSS to output a publication message as a MODIFY versus an ADD?
      2. Does the publication type selection make any difference to the system at all for internal syndication?

        • 1. Re: CSS Output Message Types
          Ron M-Oracle
          Doing External syndications handles this scenario by setting the type to MODIFY if it has already been syndicated. Your testing is showing that this isn't having the same behavior for Internal syndications.

          You could write a custom handler (like mentioned in [this previous post|https://forums.oracle.com/forums/thread.jspa?threadID=2376907] ) which checks if the spec has an already syndicated TIP and outputs a MODIFY value. You could use the ExportExtensions framework to do this.
          • 2. Re: CSS Output Message Types
            Thanks Ron. That will have to suffice as a workaround, and I appreciate the advice.