Logic Hook help to create tasks when Case is opened

[lordforbes]

Apologies if this is strictly within the realms of Sugar Pro or Enteprise, but on Sugar OS I simply want to define a set of tasks wheever a Case is created. My PHP is hopeless but I do have 20 yrs IT so I thought I'd give it a go... I can see from the forums (good here init?) that perhaps a logic hook to execute custom code after the Case has been saved sounds ideal.

Problem is, I can see only 3 or 4 examples of a logic hook, including the Deassignment Notification hook, and the advice in the wiki. These dont quite cover what I want to do, which is "after_save" of a Case, for the first time, I want to create a dozen or so tasks. I'm aware of the requirement to have the parent_type of Case and to trap the case_id to match the tasks with the correpsonding case, but to actually write the tasks to the database, should I use the Sugarbean (and if so could I be so cheeky as to ask for an example) or should I simply INSERT the records into the database...

Naturally I'd like to keep the code standardised if possible, which I guess means using the Sugarbean. I realise some of this code may be available as part of Workflow and therefore if there is a reason for the lack of exmaples then I'll understand.

Great work - both in terms of the code and the forums....

Chris
Sugar 4.5.1 (Bitrock)

[kpit]

Hello Chris,

You have found one of the missing logic hooks. I do have a patch I have to put into the baseline code that should address this missing hook.

SugarCRM did not include the hook originally as the after_save could generate an infinite loop condition. if you alter the bean after_save then try to save the current bean again. I have a method I am developing to detect and trap this type of loop and will fail on an attempt save after in the after_save hook. But this is vaporware at this time.

The biggest reason for after_save I can see is to create related records using the ID in the saved record. you can do this before the record is saved by creating a GUID and setting it in the bean id ($bean->id = create_guid();) { create_guid() is in include/utils.php } then create the related information based on the id created. This works as a work around for the lack of after_save.

[lordforbes]

Thanks for the reply Max ... I can see that most of the work in this area appears to have been responded to by you or Ken ... I'll stick with the before_save option and use the logging to work out the exact syntax to write the tasks away.. If I get this working I can see an opportunity for lots more hooks - I've been telling the clients that cerain functions were not possible but ths logic could open up a world of possibilities..!

[andydreisch]

Hey Max, be sure to submit the logic hook changes you made via the Contribution Form!!

Andy