Other solutions would have involved up front costs, which really was not available at all for this.
We don't really have an issue with raising change requests to migrate code, the problem is that normally we have to wait a couple of weeks to go through that process. A colleague did actually have a change going in a couple of days after I posted the question, and a workflow solution only required one simple form with a filter (two actions - one to cancel the change, another to cancel any open approvals). Job is all sorted, surprisingly easy really! On Wed, 10 Apr 2019 at 16:27, Support <supp...@arsmarts.com> wrote: > This is also a possible solution, but this means that Dave must have the > possibility to create a Form for that purpose on the production server, and > to remove it afterwards. This would require at the very least 2 Change > Requests, and I know environments where such Change Requests would never be > authorized.... > > On 10/04/2019 16:42, Drake Keller via ARSList wrote: > > I’ve done similar things using a staging form and an escalation. Create > the staging form as either a regular form (and import the CSV file to it) > or a view form whose source is a database table containing the data. Then > create an escalation that runs (once) on the staging form and applies the > changes. > > That should work as long as the associated workflow is in filters, and > doesn’t contain an exception for AR_ESCALATOR. > > > > > > regards, > > Aaron (Drake) > > > > *From:* ARSList [mailto:arslist-boun...@arslist.org > <arslist-boun...@arslist.org>] *On Behalf Of *Dave Barber > *Sent:* Tuesday, April 09, 2019 6:28 AM > *To:* ARSList <arslist@arslist.org> <arslist@arslist.org> > *Subject:* [E] Change Cancellations via import? > > > > All, > > > > We have a large number of open changes, at various stages from draft > through to scheduled for approval from years gone by. I'm hoping to cancel > them via a "simple" AR Import. CSV file with the change ID, and then map > the various fields. > > > > For the change request itself, this seems to work fine. But open > approvals against them - they don't get touched. > > > > But I am getting nowhere with doing a similar import against either > CHG:ChangeAPDetailSignature (which seems to do nothing) or against > AP:Signature (where you have to use zTmpAppRequest to match the CRQ > reference - but the import fails). > > > > Has anyone done such an "automation" before? Any suggestions/pointers? > > > > Regards > > > > Dave Barber > > > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist >
-- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
