Radicore Forum
Fast Uncompromising Discussions. FUDforum will get your users talking.

Home » RADICORE development » Workflow » Problem with an Add1 as the starting task of a transaction (autoincrement primary key)
Re: Problem with an Add1 as the starting task of a transaction [message #3806 is a reply to message #3805] Fri, 26 July 2013 08:55 Go to previous message
AJM is currently offline  AJM
Messages: 2367
Registered: April 2006
Location: Surrey, UK
Senior Member
I have just done a test, and it worked exactly as it should. My starting task created a new record with an auto_increment value, and this value was correctly passed to the workflow case as the context. As I cannot see a problem with my test you will have to examine your own code to see what is happening. Can you checked the following:
(1) After the call to _dml_insertRecord() in the insertRecord() method within file 'std.table.class.inc' can you confirm that the returned array contains the newly created primary key?
(2) In the _examineWorkflow() method within file 'std.table.class.inc' can you confirm that the $context string is being constructed correctly? The $input array should contain the primary key field and its value, and the call to getPkeyNames() should return the name of the primary key field.

It could be that you have some code somewhere which is replacing the generated value with zero.


 
Read Message
Read Message
Read Message
Previous Topic: Workflow with optional transition?
Next Topic: How to create CASES.
Goto Forum:
  


Current Time: Fri Nov 22 19:55:11 EST 2024

Total time taken to generate the page: 0.03325 seconds