can we have two recipient tables in ACM? | Community
Skip to main content
March 5, 2021
Solved

can we have two recipient tables in ACM?

  • March 5, 2021
  • 2 replies
  • 1193 views

How difficult is it to split existing recipient table into two recipients based on value under a particular field?

Once split will it it be possible to make workflows for both recipients using the same data in other tables in the Acm db without having to replicate these tables for the second recipient? 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Milan_Vucetic

Hi @Qurion, there is not such documentation. 1) You can define this on schema itself with sysFilter (link) 2) Table extension means you changing someting in existing table and links will be there. If you set up a new table you must define link keys for tables you want to have link. 3) You do not need separate instance.

Regards,

Milan

2 replies

Milan_Vucetic
Level 9
March 9, 2021

Hi @qurio

you can set up a custom Recipient schema.

Check it here.

Regards,

Milan

QurioAuthor
March 12, 2021

Thanks Milan for the information. The page talks about setting up a custom recipient table. it also mentions an extension table which will by default have out of box functionality linked.

 

I feel that if an extension table is used it would be ok for my requirement as all out of box functionalities will come along with that. My question on that (for which i could not find any resources online) is 

1. will we able to define access to users separately for this table or will it take the access levels defined in the original recipient table.

2. Will this extension table still be linked with all other tables in the schema.

3. will we have to run a separate instance of ACM for this or not?

 

if you could point me to where i can learn more about this would be helpful.

Milan_Vucetic
Milan_VuceticAccepted solution
Level 9
March 16, 2021

Hi @Qurion, there is not such documentation. 1) You can define this on schema itself with sysFilter (link) 2) Table extension means you changing someting in existing table and links will be there. If you set up a new table you must define link keys for tables you want to have link. 3) You do not need separate instance.

Regards,

Milan