Auto Sal updates & flagging those that shouldn't be

Natasha

UP_REBUILD_SALUTATIONS has a list_no parameter that you could use. You mentioned that the accounts you don’t want to update have an attribute. You could make a list of all the accounts that do not have this attribute and use that as the parameter in the procedure.

Of course try it out in Test first!

Sandra

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Natasha Purkiss
Sent: Wednesday, 13 March 2013 2:33 AM
To: Sandra Ashby
Subject: Re: [Tessitura Technical Forum] Auto Sal updates & flagging those that shouldn't be

Ah ok then, thanks Ken.  I guess that makes sense as I was wondering how the ‘!’ was stripped when it came to actually outputting the salutation info.

We have an attribute that we use to stop LP_CUSTOMER_RANK from updating certain accounts, so perhaps I will go down that path as I suspect there will be so few anyway.  It would be extremely helpful as you said to have something at the constituent level that didn’t involve having to add attributes or other flags etc.

I haven’t really looked at the grand possibilities of interceptors so this may be obvious, but if you were to create a service interceptor, what logic would you use to stop it at the constituent level that you couldn't do in SQL?  I’m thinking that the account would still need to be flagged in some way... wouldn’t it? 

Natasha

Hi Natasha

Sadly, that "!" code is for using in TR_SALUTATION_FORMAT, for the purpose of locking down a whole salutation type format, not at the individual constituent level.

For example, we decided to take over the esal2_desc field for an organisation name, so we've got ! in the *_namel2 format columns for relevant sal formats. That blocks them from being updated by the GenSal routine.

But there's no way to block at the constituent level, AFAIK. As I've suggested a few times, that would be an excellent use case for developing a Service Interceptor, but I don't think anyone's done it yet - I certainly haven't, in spite of having talked about it. If anyone has, raise your hand? 

Ken

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Natasha

UP_REBUILD_SALUTATIONS has a list_no parameter that you could use. You mentioned that the accounts you don’t want to update have an attribute. You could make a list of all the accounts that do not have this attribute and use that as the parameter in the procedure.

Of course try it out in Test first!

Sandra

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Natasha Purkiss
Sent: Wednesday, 13 March 2013 2:33 AM
To: Sandra Ashby
Subject: Re: [Tessitura Technical Forum] Auto Sal updates & flagging those that shouldn't be

Ah ok then, thanks Ken.  I guess that makes sense as I was wondering how the ‘!’ was stripped when it came to actually outputting the salutation info.

We have an attribute that we use to stop LP_CUSTOMER_RANK from updating certain accounts, so perhaps I will go down that path as I suspect there will be so few anyway.  It would be extremely helpful as you said to have something at the constituent level that didn’t involve having to add attributes or other flags etc.

I haven’t really looked at the grand possibilities of interceptors so this may be obvious, but if you were to create a service interceptor, what logic would you use to stop it at the constituent level that you couldn't do in SQL?  I’m thinking that the account would still need to be flagged in some way... wouldn’t it? 

Natasha

Hi Natasha

Sadly, that "!" code is for using in TR_SALUTATION_FORMAT, for the purpose of locking down a whole salutation type format, not at the individual constituent level.

For example, we decided to take over the esal2_desc field for an organisation name, so we've got ! in the *_namel2 format columns for relevant sal formats. That blocks them from being updated by the GenSal routine.

But there's no way to block at the constituent level, AFAIK. As I've suggested a few times, that would be an excellent use case for developing a Service Interceptor, but I don't think anyone's done it yet - I certainly haven't, in spite of having talked about it. If anyone has, raise your hand? 

Ken

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!