Hi Darryl, Yes there is! and in fact it seems to be in your code but commented out: /*%let mamsg=ERROR: Known Voucher File selected for APPL or PROSP Customers" Whatever you set MAMsg to be will be displayed to the user in CI Studio instead of the generic message. For example:   %if %nrquote(&SQLRC) ne %nrquote(0) %then %do; /*abort processing if last proc sql failed failed*/ /* set a customer error message for my system */ %let MAError = 913; /* optionally I can set SAS sysmsg */ %let sysmsg="Something didnt work. My explanation is here"; /* set the message that will displayed to the user. I can tell them which macro failed if that is useful, plus show my custom error message, as well as verbose text with a plain english explanation of what went wrong */ %let MAMsg = Macro[&sysmacroname.]. MAError=&MAError / Error in Rename macro. Export file does not exist. Check the log for details.; %return; %end; Regards James ... View more

Hi YY-Chen, What version of SAS Customer Intelligence are you using? Regards James ... View more

Hi @jcawesome ,   Having the DM agent on a different machine will increase fault tolerance when you lose a machine yes, but one instance per machine doesn not solve the dm -gmd support limitation. Only a single DM Agent instance can be connected to the tenant when running the metadata generation process.   Cheers James ... View more

Hi @Shubham5497 ,   In the case of the DM agent, Linux will do a good job via systemd to restart a failed instance. If there is something else going wrong with the DM Agent (for example unable to connect to CI360 cloud services or local SAS 9 install) having another instance of it is unlikely to provide any additional fault tolerance as the problem is external to the agent. In the context of batch execution of campaigns (that is measured in many minutes), waiting a few minutes for the operating system to retry a failed service is reasonable. Note that a Task/Segment that is executing when a DM agent fails is not going to failover to another instance. The failure needs manual intervention to resolve (i.e user resubmits it).   If you start more than one instance of DM Agent (first ensuring you have configured them to run on different ports and with a diffferent instanceid via the cionprem.properties file) they will all successfully connect to the tenant and participate in Task and Segment Map processing. Workload will be shared amongst the agent (not load balanced but each will process requests based on reading the next one on the queue on a first come first served basis). There is no guarantee of all tasks for a specific user session being processed by a single agent.   Importantly the Metadata generation process (dm -gmd) is not supported when running multiple DM Agents. So if you need to do this, you must ensure you only have a single DM Agent running until it completes.    There is not any documentation on this, so official support may be hard to find. Regards James ... View more

Hi @sbonisoma, the stored process runs in the on-premise server component of the architecture with Engage Direct. The creation of the stored process is a developer/administrative task that is done in SAS Management Console.  The documentation for Custom Process Nodes can be found here: https://go.documentation.sas.com/doc/en/cintcdc/production.a/cintug/seg-process-stp.htm. Regards James   ... View more

Hi @alko13 , it best fits on the midtier. Having said that, when comparing Engage Direct to other 9.4 based applications, much of the solution is cloud based (for example the UI, identity,  authentication authorisation, scheduling as a few examples). Consequently much of the traditonal 9.4 workload is not using the main components of 9.4 for the heavy work, but rather a very light purpose. We find many installations are co-locating all 3 tiers because metadata and midtier are so lightly used or perhaps on 2 tiers not 3.  The architecture decisions will depend on your implementations usage, workload and organisation's IT standards.   Regards James ... View more

HI @sbonisoma , this can be achieved using a Custom Process Node in the Segment map. The custom process needs to be coded appropriately (prepare the data for the API call, make the API call and process the results), so its more than just configuration. However its a one time activity, and the custom process is then a reusable asset for any number of segment maps.   Regards James   ... View more

be sure to revert disablemetaupload to true, so that the upload doesnt happen un-necessarily on subsequent restarts of the DM Agent. ... View more

In CI6 the relationships between tables defined in the Info map changes what is available in "Select Node Rules" inside the Select Node, when using fields that are from tables that are not in the primary subject table i.e. on the many side of the join. CI studio will use the join type to change which select rules are available: Any value meets these criteria One value meets these criteria More than one value meets these criteria No value meets these criteria All values meet these criteria. See Page 189 of the CI6.6 User Guide for more details. If you user a data item from the many side of the join and chose a rule other than "Any Value meets" then you will see the SQL change.   HTH, James ... View more