on 2020 Sep 01 1:38 PM
Hi all,
I created a Custom Object named ScLc that contains servicecall as a field.
what i am trying to do is to create a business rule tht whenever the servicecall change, a custom object ScLc is created.
I dont know how to use custom object in a business rule, i tried with the example in FSM documentation but it didnt work well.
i also wanna know what is the query to extract my custom object.
Thanks and regards,
Wail
Request clarification before answering.
Hi Wail,
If you haven't figured it out yet and for any other community members' benefit, this is what I would suggest.
Your business rule needs to have an additional variable. Let's call it metaScLc. It should be an object for Object Type UdoMeta. CoreSQL clause should be: metaScLc.name = 'ScLc'
Then your action to create a custom object should be like this:
Action = Create Object
Execution Count = 1
Object Type = UdoValue
Object Version = empty (use the latest)
Fields:
meta = ${ScLcMeta.id}
udf.servicecall = ${serviceCall.id}
I presume that your field in the custom object is 'servicecall' and your business rule is based on ServiceCall object, hence you should have serviceCall variable already.
And this is pretty much all that you need to create a custom object instance via business rule.
Now I think it's quite clear how to query your custom object. For example, the below query will give you back 2 columns for all your custom object instances: your custom object IDs and corresponding service calls.
SELECT udov.id, udov.udf.servicecall as servicecall
FROM UdoValue udov
INNER JOIN UdoMeta udm
ON udov.meta = udm.id
WHERE udm.name = 'ScLc'
Hoping this will help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi andrei
it's perfect 🙂
thank you alot for your help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
10 | |
5 | |
4 | |
4 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.