Tim, Due to the fact that Mid-Tier is nothing more than an API Client of the Remedy Server, I can tell you that all things are possible through the API :)
The trick is figuring out what fields are set to what values via what workflow. Mid-Tier executes active links to populate various things before communicating with the server, there is not specific need to replicate everything that the AL's are doing, just the part where they are communicating with the Remedy server...so, in this case, AL/Filter logs are going to be the most important part. If you can capture the 'normal' operations in logs, you should be able to push the same values to the same fields, thus replicating the overall process. On Fri, Jun 12, 2015 at 5:25 AM, Tim Lank <[email protected]> wrote: > ** > Is it supported and possible to create a TAS via TMS:Task with the API, > associate it properly with an existing 'No Impact' CRQ in 'Draft' status > (also created via API) and have all of the OOTB workflow operate properly > as if it were done through the Web UI/MidTier? > > When we do this, we end up with an (ORA-01407: cannot update > ("ARADMIN"."T1269"."C8") to NULL) (ARERR #552) when moving CRQ status from > (2) Request for Change to (3) Planning in Progress. I'm assuming this is > the TMS:SummaryData table complaining about the 'Short Description' field > not being populated. Is this something that is normally handled by OOTB > workflow? > > ARS: 7.6.04 SP5 > ITSM: 7.6.04 SP4 > C-API - ProdVers: Server API Version 7.6.04 SP5 201308012025 (By way of > ARSperl v2.00) > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
