Work page is taking as temporary object.


I have created a class group and defined the keys as "pyID".
I created the work class as belongs to that class group created earlier.
I tried running the flow under the work class and it is not creating the work Id as it is taking as temporary object.

I traced it, the problem is coming from the 8th step of "AddWork" Activity precondition (isPageWriteableToDB).

In that function "return cd.canWriteInstances();" function is returning NULL.
I have defined the classes correctly and those mapped correctly to pc_work table.

Any help greatly appreciated.


**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.


Keep up to date on this post and subscribe to comments

January 13, 2010 - 10:45am


Please verify Data-Admin-DB-ClassGroup instance settings.

Thank you,

January 14, 2010 - 6:33pm

A checklist for you to verify:

(1) In the flow rule's Process tab, is 'Creates a new work object?' checked?

(2) Assuming #1 is true, in the Work Object Creation Settings section, is 'Temporary Object?' checked?

(3) What is the value of pyTemporaryObject on pyWorkPage? Is it being set by a model record?

(4) When you trace the flow and the activity rule AddWork is called, the is the step that calls GenerateID skipped?

(5) As mentioned, double-check the Data-Admin-DB-ClassGroup record that corresponds to the class you designated as class group; insure the pyID property is listed as the key.

January 20, 2010 - 12:20pm

Yes, Data-Admin-DB-ClasGroup is not having keys.
Giving the keys there solves it.

Thanks a lot

July 3, 2014 - 8:08am

Helped me even now. After 4 years since the solution was posted. The class keys were missing and the class defn was "Is a Class Group". Thanks for the solution.