PT Profile Roles - Revision history

Mcarroll: /* Customizations */

2010-04-23T19:56:55Z

‎Customizations

Mcarroll: /* Customizations */

2010-04-20T20:54:57Z

‎Customizations

Mcarroll at 16:05, 29 March 2010

2010-03-29T16:05:01Z

Mcarroll: /* Customizations */

2010-03-29T16:04:15Z

‎Customizations

Mcarroll: /* Customizations */

2010-03-29T16:02:35Z

‎Customizations

Mcarroll: /* Customizations */

2010-03-29T16:02:23Z

‎Customizations

Mcarroll at 15:58, 29 March 2010

2010-03-29T15:58:25Z

Mcarroll: /* Configuration Points */

2010-03-29T15:57:28Z

‎Configuration Points

Mcarroll: moved Profile Roles to PT Profile Roles

2010-03-26T19:10:12Z

moved Profile Roles to PT Profile Roles

Renee.mckechnie at 23:02, 24 January 2010

2010-01-24T23:02:42Z

@@ Line 13: / Line 13: @@
 ## Copy the [[PT_Profile_Roles_Component|ProfileRoles Component]] component from the ADF apps directory to your local site components directory ''/MySite/_cs_apps/pt_profile/components/profileRoles.cfc''.
 ## In the ''setRolePermission'' function, add a new case statement for the role name.  Add your logic to set the roles permmission.
 # /ADF/apps/pt_profile/datasheet-modules/datasheet-action-edit-delete-view.cfm
 ## The datasheet action column will render a view button for the profile page.  This needs to be setup based on the profile role.  Update the top of the script to set the profile role to use as the view button.

@@ Line 13: / Line 13: @@
 ## Copy the [[PT_Profile_Roles_Component|ProfileRoles Component]] component from the ADF apps directory to your local site components directory ''/MySite/_cs_apps/pt_profile/components/profileRoles.cfc''.
 ## In the ''setRolePermission'' function, add a new case statement for the role name.  Add your logic to set the roles permmission.
-# [optional] /ADF/apps/pt_profile/customcf/profile_manager.cfm
+# /ADF/apps/pt_profile/customcf/profile_dashboard.cfm
-## Profile Manager script iterates over the profile roles to display what the logged in user has permissions to access/view.  To make a new role render, this needs to be updated manually.
+## Profile Dashboard script iterates over the profile roles to display what the logged in user has permissions to access/view.  To make a new role render, this needs to be updated manually.
 [[Category:Profile]]
 [[Category:Customization]]

@@ Line 10: / Line 10: @@
 ## Populate SUBSITE_ID by creating a new subsite for the profile pages and update the ID in the configuration file.  See the [[PT_Profile Subsites|Subsites]] wiki page for additional details.
 ## Populate TEMPLATE_ID by creating a new template for the profile pages and update the ID in the configuration file.  See the [[PT_Profile_Template|Profile Template]] wiki page for additional details. (Note: This step is optional - you can also use one template for all profile roles.)
-# Depending on the complexity of your roles and how many sites are implementing the profile app, you can either update the [[ProfileRoles_Component|ProfileRoles Component]] with the new roles.
+# Depending on the complexity of your roles and how many sites are implementing the profile app, you can either update the [[PT_Profile_Roles_Component|ProfileRoles Component]] with the new roles.
-## Copy the [[ProfileRoles_Component|ProfileRoles Component]] component from the ADF apps directory to your local site components directory ''/MySite/_cs_apps/pt_profile/components/profileRoles.cfc''.
+## Copy the [[PT_Profile_Roles_Component|ProfileRoles Component]] component from the ADF apps directory to your local site components directory ''/MySite/_cs_apps/pt_profile/components/profileRoles.cfc''.
 ## In the ''setRolePermission'' function, add a new case statement for the role name.  Add your logic to set the roles permmission.
 # [optional] /ADF/apps/pt_profile/customcf/profile_manager.cfm

@@ Line 9: / Line 9: @@
 # Update the [[PT_Profile Site_Configuration|Site Configuration]] with the new role.  Add a new tag under the <ROLES> tag with the name of the role.  Next, you'll add the SUBSITE_ID and TEMPLATE_ID tags.
 ## Populate SUBSITE_ID by creating a new subsite for the profile pages and update the ID in the configuration file.  See the [[PT_Profile Subsites|Subsites]] wiki page for additional details.
-## Populate TEMPLATE_ID by creating a new template for the profile pages and update the ID in the configuration file.  See the [[PT_Profile_Template|Profile_Template]] wiki page for additional details. (Note: This step is optional - you can also use one template for all profile roles.)
+## Populate TEMPLATE_ID by creating a new template for the profile pages and update the ID in the configuration file.  See the [[PT_Profile_Template|Profile Template]] wiki page for additional details. (Note: This step is optional - you can also use one template for all profile roles.)
 # Depending on the complexity of your roles and how many sites are implementing the profile app, you can either update the [[ProfileRoles_Component|ProfileRoles Component]] with the new roles.
 ## Copy the [[ProfileRoles_Component|ProfileRoles Component]] component from the ADF apps directory to your local site components directory ''/MySite/_cs_apps/pt_profile/components/profileRoles.cfc''.

@@ Line 13: / Line 13: @@
 ## Copy the [[ProfileRoles_Component|ProfileRoles Component]] component from the ADF apps directory to your local site components directory ''/MySite/_cs_apps/pt_profile/components/profileRoles.cfc''.
 ## In the ''setRolePermission'' function, add a new case statement for the role name.  Add your logic to set the roles permmission.
-* [optional] /ADF/apps/pt_profile/customcf/profile_manager.cfm
+# [optional] /ADF/apps/pt_profile/customcf/profile_manager.cfm
-** Profile Manager script iterates over the profile roles to display what the logged in user has permissions to access/view.  To make a new role render, this needs to be updated manually.
+## Profile Manager script iterates over the profile roles to display what the logged in user has permissions to access/view.  To make a new role render, this needs to be updated manually.
 [[Category:Profile]]
 [[Category:Customization]]

@@ Line 5: / Line 5: @@
 == Customizations ==
-* /SiteName/_cs_apps/config/ptProfile.xml
+Customizing the profile roles is a valuable piece to the profile application.  Following the instructions below to add a new role:
-** [[How_to_add_profile_role | Add a new profile role]]
-** See the [[PT_Profile_Site Configuration|Site Configuration]] for details on updates for additional roles.
+# Update the [[PT_Profile Site_Configuration|Site Configuration]] with the new role.  Add a new tag under the <ROLES> tag with the name of the role.  Next, you'll add the SUBSITE_ID and TEMPLATE_ID tags.
-* [[PT_Profile_Roles_Component|ProfileRoles Component]]
+## Populate SUBSITE_ID by creating a new subsite for the profile pages and update the ID in the configuration file.  See the [[PT_Profile Subsites|Subsites]] wiki page for additional details.
 * [optional] /ADF/apps/pt_profile/customcf/profile_manager.cfm
 ** Profile Manager script iterates over the profile roles to display what the logged in user has permissions to access/view.  To make a new role render, this needs to be updated manually.
 [[Category:Profile]]
 [[Category:Customization]]

@@ Line 1: / Line 1: @@
 == Overview ==
-Profile roles are set up through the [[PT_Profile_Site_Configuration|Site Configuration]] and [[ProfileRoles_Component|ProfileRoles Component]].  These roles establish permissions for the profile and determines which subsites and/or templates the profile page will be derived from.  This configuration allows the same profile information to be used for multiple displays throughout the site.
+Profile roles are set up through the [[PT_Profile_Site_Configuration|Site Configuration]] and [[PT_Profile_Roles_Component|ProfileRoles Component]].  These roles establish permissions for the profile and determines which subsites and/or templates the profile page will be derived from.  This configuration allows the same profile information to be used for multiple displays throughout the site.
 Profile roles will differ depending on the purpose of the application.  For example, if the profiles were implemented in an educational institution, roles could be 'student', 'faculty', and 'staff;' if implemented for healthcare, the roles could be 'doctor', 'surgeon', 'nurse', and 'staff.'
@@ Line 8: / Line 8: @@
 ** [[How_to_add_profile_role | Add a new profile role]]
 ** See the [[PT_Profile_Site Configuration|Site Configuration]] for details on updates for additional roles.
-* [[ProfileRoles_Component|ProfileRoles Component]]
+* [[PT_Profile_Roles_Component|ProfileRoles Component]]
 * [optional] /ADF/apps/pt_profile/customcf/profile_manager.cfm
 ** Profile Manager script iterates over the profile roles to display what the logged in user has permissions to access/view.  To make a new role render, this needs to be updated manually.

← Older revision	Revision as of 19:10, 26 March 2010
(No difference)