How can we generate a Create Account task through Analytics

[jbaskaran]

HI all,

Expectation: Create account (Endpoint A) once the user got provisioned into one of the entitlements under different endpoint (Endpoint B) & need to generate a Update Account Task, if the user is provisioned to that account but Cp is null or false. We have created the analytics query & based on the output 'Update account task' gets generated but facing issue in generating the 'Create Account Task'.

Note : We wanted to use analytics to generate the task since the account gets updated based on the account attribute & not user attribute. So, we can't go by using Rule.

As there is no option to generate Create Account Task using analytics, can someone please suggest the alternate way to achieve the same.

Thanks

[sk]

@jbaskaran : Can you clarify this part of the requirement?

We wanted use analytics to generate the task since the account gets provisioned/updated based on the other endpoint attribute. So, we can't go by using Rule

I am clear on this part, if user requests an entitlement in Endpoint B upon completion he needs to get account created in Endpoint A(if this is the only requirement then you can use EntitlementMap to achieve) but additional condition you mentioned in note is not clear

[jbaskaran]

@sk 

We wanted to use analytics to generate the task since the account gets provisioned/updated based on the other endpoint attribute. So, we can't go by using - I mean that we can't generate 'Update Account' by using 'Update Rules' since we don't have any 'User attribute' which identifies that the particular Account is provisioned, here it is based on the 'Account attribute'. 

[sk]

@jbaskaran : Okay in that case for create account can you use EntitlementMap feature? Do you have any entitlement under Endpoint A which can be added under entitlement map on entitlement which user is going to request under endpoint B?

[jbaskaran]

@sk - We don't have any Entitlement under endpoint A, it's based on the entitlement in endpoint B. Account gets provisioned to endpoint A.

Thanks

[rushikeshvartak]

update user's attribute and use user's attribute in endpoint 2

[jbaskaran]

@rushikeshvartak - If I understood correctly, you're asking to update a new user attribute (CP) through which we can identity that user has an entitlement provisioned in Endpoint B so that we can generate a Create Account Task for endpoint A using Rules. 

Thanks