In this article
In the config hub block you can configure the data tables involved in the hub program, and relations between the tables.
At a minimum, the config hub section need to specify which hub the Pulse program should be tied to, and a dynamic reference to the survey selected (which is used when opening the report for a specific survey).
config hub {
hub: 123456
table survey = @urlParams.surveyResponseTable
}Depending on the configuration of the program (especially reporting), it may be desirable to add references to other tables in the config hub section, from database designer (hierarchies) and/or custom data. These are optional:
table endusers = EndUsers.EndUserList_1234 //custom data table with the end users assigned to the program, if those are created from contacts
table surveylist = PulseProgram123.Surveys //the surveys in the program
table hier = dbdesigner.123456 //the table of the organization hierarchy (from hierarchy management)
table roles = Authorization.UserRoles //custom data table with roles of the end users (like manager, hr)
table userNodes = Hierarchy12345.NodeAssignments //custom data table with node assignments from hierarchy management
// User access claims tying user to role or
userProperty claim #myRole {
joinKey: roles:Username // username to match on currently logged in user
value: roles:Role // roles
}
userProperty claim #nodeId {
joinKey: userNodes:UserName //username to match on currently logged in user
value: userNodes:NodeId //hierarchy node assignments
}