Hello, AML 7.1 does not have workflow similar to 6.3.  7.1 does have custom queues functionality. Here's an overview:   •Queues are used to control user access to entities (customers or external parties), cases, reports and CDD Reviews. •An entity that alerts can be routed to a new queue or to another queue while remaining in the original queue.  This allows simultaneous review of entity alerts by different users.  For example, the watchlist team reviews the watchlist alert while the standard review team reviews other alerts. •Queues can be configured so that the Alert Generation Process (AGP) will route entities to a particular queue.  The UI will use the information when displaying triage lists to users. •In addition to the entities referenced above, alerts also can be assigned to a particular queue during AGP routing. Queue Access •Users have access to a queue and to the items in the queue only with membership (direct or inherited) of the role that is configured for the queue access. •Roles are used by the investigation UI to filter items that a particular user may access.  In addition, REST services are also performing additional validation for alerts to ensure only authorized users can access a particular item. Entity triage •If AGP routing to queues is enabled for entities then The “All entities”, “My entities” and “Available entities” lists will only display the entities from queues for which a user as access rights and where the entities have not been assigned to any queue. Ownership control (assignment to specific user) works the same way as it worked before HF5 was applied. •Entities might be assigned to multiple queues.  For example, an entity is assigned to the Watchlist queue and the Employee queue for review.  A user who has access rights to both queues will see the entity listed twice in the entity triage page, once for each queue. The alert count and aggregated amount will reflect the total count of all alerts for the entity. • Cases, Reports, and CDD Reviews Triage •Triage lists for cases, reports and CDD reviews will display only the items from queues for which a user has access rights or items that have no queue assigned. Alerts •AGP routing to queues can be also be enabled for alerts. If an alert is assigned to a queue, logic in the UI and REST services will validate users have access rights to the alert.   •If a user does not have access rights to the queue, the user will be unable to open the alert from the UI or select the alert for triage. This is controlled in the Admin tab with the enforceQueuesForAlerts preference. •As additional security, customers may enable alerts filtering so that alerts are hidden from users who do not have access rights. This is controlled in the Admin tab with the hideAlertsFromUnauthorizedQueues preference. Entity details page •All alerts for an entity are displayed on the entity details page.  However, only alerts from the queues that a user has access rights may be triaged (i.e., closed, suppressed, added to a case). •If a user without access rights attempt to select an alert in a queue where they do not have access rights, a warning message will be displayed indicating the user is not authorized to view the content. •Double-click of alerts is also not allowed.  For example, the alert details page cannot be opened for alerts in queues where a user does not have access rights. ... View more

Anusha,   CDDR _c910 - Country Max Attribute Not a calculation rule...If there are multiple scores for the same country attribute, uses the one with the maximum score and Auto High flag. CDDR_C920 - Country Aggregation Is a calculation rule...It is the weighted sum of country attribute scores divided by the weighted sum of max country scores. CDDRG_X010 - Category Aggregation Rules Is a calculation rule...is the calculated weighted sum of Category Scores CDDRG_X015 - Strategy Rules Is a calculation rule...This is used to modify customer score based on the length of time as a client.   Hope this helps.   ... View more

Hi, Not sure what elements you are most interested in, but generally, AML 7.1 runs on the SAS 9.4 platform and adds the following significant functions: Re-designed UI screens Performant services layer (REST) Custom queues  Enhanced scenario administration Scenario segmentation  Customer Due Diligence (CDD) Integrated Funds Tracker visualization Entity level alerting Entity Triage SOLR Search Targeted Search Integrated regulatory reporting Included operational reports Localization of UI in multiple non-English languages     ... View more

Typically risk classifiers are managed within the UI using the List Manager screen that is located within the Admin console.  This links into the risk classifier table in the Knowledge Center data schema.  In the FSK_Risk_Classifier table it is defined for each classifier to which data point it refers in the Core schema (most are in Party DIM). So the risk classifiers are set up through the UI and the data it looks at (e.g. in party dim) are loaded in batch as part of the regular ETL that usually precedes running the AGP.  See attached screen shots.  While it may be possible to load the risk classifier data using a back end process, this is not a standard automation and with the small set of classifiers you mentioned, probably not worth automating.  However, SAS Services may be able to help build an automated process if desired.     ... View more

Hello.     Risk assessments are an optional component of SAS Anti-Money Laundering. If System Administrators at your site enabled the risk classification process, users with the Access My Risk Assessments or Access Available Risk Assessments capability can access My Risk Assessments and Available Risk Assessments queues.   A risk assessment is a proposal to change a customer's risk classification. Each risk assessment has a current risk classification and a proposed risk classification. The objective is to use the tools and information that SAS Anti-Money Laundering provides to determine whether the proposed risk classification should be accepted and closed, or rejected and closed. Risk assessments come from two sources:   SAS Anti-Money Laundering system generated. The risk classification process runs risk classifiers across customer data. Manual creation. Users manually create risk assessments when they observe suspicious behaviors that might not be detected by the risk classifiers. The risk assessment process is executed less often than the risk classification process. Although most institutions determine their customers' risk classifications on an annual basis, customers might be classified for any period of time that is deemed appropriate. The period at which sites execute the risk assessment process is called the risk assessment period. The risk assessment process applies a weighted scoring algorithm to determine a proposed risk classification for each customer's risk assessment. The process then routes risk assessments to the user or group as specified by the risk assessment routing rules.   The product documentation fully describes the risk assessment functionality and administration.  Please reach out to SAS Technical Support if you need help accessing the online documentation. ... View more

Some background: The run date used when the AGP is executed is derived from the content of the fsk_job_calendar table. When the AGP runs, the run date applied will be the earliest business day entry in the fsk_job_calendar table where the ‘status_ind’ field is set to ‘N’, indicating that this is the earliest business day for which the AGP has NOT yet been run. When the AGP executes for a run date the ‘status_ind’ field for that date is flipped from ‘N’ to ‘Y’, indicating that the AGP has already been executed on that date. The fsk_job_calendar table also has Day, Week, Month indicators that are used to determine which scenarios are executed on any given run date based upon each scenario’s stated execution frequency (e.g., daily, weekly, monthly).   For the question, you would have to reset the fsk_job_calendar entries so that all records prior to the start date (2 years ago) have a ‘status_ind’ set to ‘Y’, and all other records have a ‘status_ind’ set to ‘N’. The next AGP run will then execute for the intended start date (2 years ago). Each subsequent AGP run will move to the next indicated business day in the fsk_job_calendar table. You will have to execute the AGP a total number of times that covers each day over the required 2 year period.   The following macro may be useful in initializing the fsk_job_calendar table to begin at the intended start date 2 years ago…   %macro set_run_date(RUN_DATE=);     proc sql;    update db_kc.fsk_job_calendar set status_ind ='N';    update db_kc.fsk_job_calendar set status_ind='Y'    where datepart(calendar_date) < &RUN_DATE.d;   quit;     %fcf_get_runasofdate;   %put &runasofdate;   %mend; ... View more

Can you please attach a screen shot of the page where the field label needs to be modified? Thanks. ... View more