This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
The only time SequenceNum and UpdateSeq should be the same is when the entry and its invites are first created. After that you either update SequenceNum when Rescheduling/Cancelling OR update UpdateSeq when sending an Info Update.
You should note that the update value is NOT simply (current item value)+1. It is MAX(current SequenceNum, current UpdateSeq)+1.
So in your scenario your 2 (SequenceNum, UpdateSeq) values would start at 1,1. They then go to 2,1 on the reschedule and then to 3,1 on the Cancel.
If you had done 3 info updates before the first reschedule (e.g. Agenda changes or adding new invitees) then your values would have gone from 1,1 to 1,2 followed by 1,3 and 1,4. The reschedule would then go to 5,4 and the cancel to 6,4.
You will also need to include an updated $CSWISL on the docs so that Notes knows what items are changing with each update/reschedule. You currently do NOT include that and that will cause you problems if you expect Notes C&S to be able to consume your hand crafted workflow.
Bruce
IBM
Feedback response number BKANA4JNJE created by ~Lex Nontookonynivu on 11/23/2015
Your sequencing info is probably wrong
Return to top
. . Your sequencing info is probably wr... (~James Preresas... 23.Nov.15) 
