All the transactions triggered by a specific action (e.g., active link push field, which in turn triggers filter processing) are processed in a single transaction. If an error is encoutered, the entire set of transactions are rolled back. If not error is encountered, the entire set of transactions are committed.
A direct SQL (update, insert, etc.) will not trigger filter processing on the target form. If you want to use SQL to update the records, you need to use either the DB view (e.g., HPD_HELP_DESK) or the DB table (e.g., T1234). The column names in the view and the table will not exactly match your field names. On Mon, May 7, 2012 at 9:23 AM, smiley <nti...@umich.edu> wrote: > okay I see that Direct SQL will do a 'commit' for me. > (I'm in ITSM 7.6.03 on MS sql server) In an Active Link. > > But I don't see why 'Push Fields' wouldn't do a commit for me too. > > So if they both do 'commits' for me without being specified, I think the > Direct SQL will NOT trigger the filters that run on Modify/submit etc. > > Then I think maybe the 'Push Fields' will trigger the filters that run on > Modify. > right? > > thanks! > > -- > View this message in context: > http://ars-action-request-system.1093659.n2.nabble.com/to-commit-or-not-to-commit-that-is-the-question-tp7535439p7535471.html > Sent from the ARS (Action Request System) mailing list archive at > Nabble.com. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
