This idea has been merged into another idea. To comment or vote on this idea, please visit GIN-I-4755 Site Wise Agent Mapping .
WE HAVE MULTIPLE ORGINATION SITES AND CUSTOMER IS ALWASY SAME FOR THE ORGINATION UNIT FOR OF ITS CUSTOMERS. THEN PLEASE ADVISE TO MANAGE DIFFENENT AGENT FOR THE SAME CUSTOMER WHICH IS SITE SPECIFIC
THANKS
RAJEEV KANSRA
M-9215587111
Rajeev Kansra
ON THE ONE HAND YOU ARE KEEPING THIS IDEA AS OPEN ON THE OTHER HAND U ARE TAGGING IT AS UNLIKELY TO IMPLEMENT. PLEASE CLARIFIY
THANKS
RAJEEV
M-9215587111
Attachments Open full size
We understand your requirement, but the solution suggested earlier is the only workaround option in the system.
In the present architecture, the desired requirement is not available, still we are keeping the idea as open for future scope of working.
Attachments Open full size
SORRY WE KNOW THAT WAY WHAT WE WANT NO DISCRETION OF THE USER. FROM TIME TO TIME DIFFERNT AGENT IS ASSIGNED TO THE MASTER SO WANT IT WITH THE TRACK OF WHICH ONE WAS THE PREVIOUS AGENT FROM THIS PERIOD TO PERIOD AND HENE FORTH THIS IS THE AGENT FROM THIS PERIOD TO THAT PERIOD
Attachments Open full size
For the scenario stated above, Agent Name tagging should be avoided in customer master.
At the time of transaction for each site/unit, user can select respective agent name for the transaction and proceed.
Attachments Open full size