Unanswered questions

In today’s quickly changing job market, what an employee understands today could be obsolete tomorrow. Companies can no longer manage their personnel by relying exclusively on job titles or degrees. Instead, they need to know exactly what capabilities their staff have and where there are gaps.This trend has made Skills Intelligence one of the most important themes in current corporate learning. Skills intelligence, integrated with SAP SuccessFactors, one of the world’s leading cloud-based Human Capital Management systems, transforms traditional HR into a data-driven dynamo. This tutorial explains to anyone undergoing SAP SuccessFactors Training why skills intelligence is important. What is Skill Intelligence? Skills Intelligence is the smart way to collect, analyze and act on data about employee skills throughout a business.Skills intelligence breaks down the job of a person into individual competencies, such as data analysis, Java programming or public speaking, rather than labeling t

I am promoting a SQL Catalog Item from Environment A to Environment B in Ataccama ONE.The SQL Catalog Item does not exist in Environment B, so it is expected to be created as part of the import. The required Location/Source GUID mappings are already configured.The challenge is that the SQL Catalog Item contains an SQL query with an environment-specific schema name.For example, in Environment A, the query contains:FROM ENV_A_SCHEMA.brz_pa_oracle_view.table1WHERE Report_Snapshot_Date = ( SELECT MAX(Report_Snapshot_Date) FROM ENV_A_SCHEMA.brz_pa_oracle_view.table1)LEFT JOIN ENV_A_SCHEMA.brz_pa_oracle_view.table2 pmIn Environment B, the schema should be: FROM ENV_B_SCHEMA.brz_pa_oracle_view.table1 and similarly for the other tables.What I triedBased on the Environment Mapping documentation, I configured a scalar mapping for the Location: { "location.name": [ { "pattern": "^<ENV_A_SCHEMA>$", "replacement": "<ENV_B_SCHEMA>" } ]}The Location mapping works a

Version 16.3.0, on PaaS.Normally, our Ataccama team gets access to all workflows in the admin centre.I’ve got a use case where we want to allow users with 1 RDM role to run 1 workflow. They should not be able to run any other workflows.I’m trying to play with the intercepturls in the git project.I tried giving access to the welcome page, but it comes up weird. Normal welcome page:   Welcome page for my test user:   How do I neatly provide the access to just that 1 workflow but also allow them to navigate to it? Or am I stuck having to give them the exact URL? I can’t give /console/wfConfigs/** to allow them to browse to the workflow, because that would automatically allow them access to all workflows.Any ideas?