ServiceDesk

 View Only
  • 1.  Customer Survey Issue - Part 2 (SD 7.5)

    Posted Aug 02, 2013 12:02 PM

    Hi again,

    Since my last post regarding how to get custom data into the SD.CustomerSurvey project, I have created a new integration (User Defined with DB mapping) that added the one int value that's going to store the answer to the one additional question on the survey to the database.  I also created the Profile Definition so that I can add it to the existing Customer Survey web part.  That all works, up until I take the survey and then click to close the form when I'm done.

    Once the system finishes with the End component of the workflow, it does its cleanup routine.  Unfortunately, during the cleanup routine, the system builds a delete query and deletes all of my custom data from the database.  When the project was running, I could see the custom data both from the ProcessManager portal and the database.

    Any way I can prevent this?  It doesn't make much sense to me.

    Thanks!



  • 2.  RE: Customer Survey Issue - Part 2 (SD 7.5)
    Best Answer

    Broadcom Employee
    Posted Aug 03, 2013 12:40 PM

    I believe what is happening is the setting Data Cleanup Policy that is found on the Publishing tab of the Project Properties is removing the custom data. You can change this setting to be set @ No Cleanup and see if that makes a difference.

     



  • 3.  RE: Customer Survey Issue - Part 2 (SD 7.5)

    Posted Aug 03, 2013 01:57 PM

    I'll give that a shot, thanks!



  • 4.  RE: Customer Survey Issue - Part 2 (SD 7.5)

    Posted Aug 05, 2013 10:04 AM

    I set it to No Cleanup and it's working as expected now.  Thanks again for your help!  One quick question regarding the No Cleanup policy - are there any detrimental side effects to having it this way? 



  • 5.  RE: Customer Survey Issue - Part 2 (SD 7.5)

    Broadcom Employee
    Posted Aug 22, 2013 05:24 PM

    I guess that depends on what you consider detrimental. Workflow doesn't have any database clean up functionality built into it like the SMP does. So the only way WF cleans up entries in the database is based on the Clean up policy. However if you enable the policy as soon as there are no active tasks for the process the data is gone.

    So leavng the policy set to No Cleanup will allow you to actually keep & review the data, but you will need to perform your own cleanup on the database if your company decides you only want to save data for a certain time frame.