Force Request field tokens to save to the database?
Anyone have a method for forcing Request field tokens to save to the database? We have created Requests using the KCVS_UTILITIES.create_request that copy tokens from the Parent to Child, but the tokens aren't saved to the database for the Child request (even though they show in the form), and so security evaluation using the tokens doesn't work correctly.
Re: Force Request field tokens to save to the database?
You say that the child requests are created via the kcvs_utilities, so that tells me that the request is created without using the web interface. So, then you open the request in the web interface and you see the values, but then you say that the values are not in the database. I think that either a) you are looking in the wrong place in the database or b) you are somehow blanking out the values without realizing it.