• State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 96 subscribers
  • Views 2989 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Schedule Process with No Base Object

dan
over 7 years ago

Using v7.1. Is it possible to kick off a scheduled Process Orchestration process chain with no base object? There's some customisation that I'm thinking about doing and as a scheduled task I want to stamp some records and make a foreign key for the stamps in a custom table for some business logic groupings. This process doesn't need a base object and I don't think I want it to have one because I want it to definitely fire only once at the scheduled time. If the process gets fired off for multiple base objects, I would probably run into a problem with concurrency corrupting the stamps and references I mentioned. So anyway to achieve this?

  • 0 over 7 years ago
    Hi Dan,
    No, every process has a base object. But for this kind of process, you can use the DialogSchedule table as your base object. Then you can use the generating condition to limit execution to your specific schedule.
  • 0 over 7 years ago
    I could set the process to use the DialogSchedule table but what event would I use to trigger it. I just want it to be a timed process, kicked off once every day. It doesn't make sense to make it an Insert, Delete or Update on the DialogSchedule table.
  • 0 over 7 years ago

    Take a look at process automation in process orchestration.

    Setup a process automation object, select a base object and custom event to be fired with a whereclause, and assign a schedule object to it.

    Some people use the resulting DialogSchedule object as base object (which is what George suggested) and define a whereclause to only fire on the one schedule object, while other people define their scheduled processes on DialogDatabase, in which case you can generally omit a whereclause since there is usually only one object ever in that table.

    In these cases, the generated processes have nothing to do with the associated base object, it's just there to enable and control process generation. You can also define them on all sorts of base objects but those are the two I've encountered most for scheduled processes.