Writer instructions | ||
Purpose | Use this page to display a banner announcement on each page of the space. Create the Space announcements page in the master space, outside of the Home branch. You can version the Space announcements page to enable different banners to be published into different target spaces, however, the banner that is displayed in the versioned (master) space itself only displays the most recently-published banner. If you find errors in the banner area of your versioned space and you are sure the Space announcements page is set up correctly, try publishing the page to the same space. For more information, see Space-announcements-banners. | |
Removing | When an announcement is no longer needed, remove the BMC Space Banner macro. | |
Translation | Localized spaces using the L10n Viewport theme must change the name of this page to Space announcements l10n. See Configuring-the-Scroll-ViewPort-theme-for-translated-spaces. | |
Usage | Choose one or none of the following BMC Space Banner macros. If your space requires another kind of announcement, you can use this page in coordination with your team lead and editors. | |
Data privacy specification
The Data Privacy Specification screen shown in the following figure is displayed when you select Option 8 - Data Privacy from the Extract Menu.
Data Privacy Specification
Command ===>
Select Disguise Method for Extract File:
Disguise Extract File ===> 3 ( 1 = Use DCF; 2 = Use DPR; 3 = No)
DCF: Control File ===> 'TSOID01.FRSAMP.DISGUISE'
DPR: Repository Name ===>
Project Name ===>
Retain pre-disguise file ===> Y ( Y = Yes; N = No)
Create Audit Trail ===> N ( Y = Yes; N = No)
Audit Trail prefix ===>
Use this screen to specify data privacy information for this extract request.
Select Disguise Method for Extract File
Disguise Extract File
Specify whether File-AID/RDX should disguise the extracted data as part of the extract batch job or not. When set to 1 (DCF) or 2 (DPR), all extracted objects which have disguise criteria defined in the Disguise Control file (DCF) or in the Dynamic Privacy Rules Project (DPR) will be disguised.
1 | Use DCF. Disguise the extracted data using a disguise control file (DCF). This option requires installation of Compuware’s BMC Compuware File-AID/Data Solutions. When returning to the Extract Menu, the DISGUISED indicator in front of the extract file is displayed. |
2 | Use DPR. Disguise the extracted data using a Dynamic Privacy Rules Project (DPR). This option requires installation of Compuware’s BMC Compuware File-AID/Data Solutions and the BMC Compuware File-AID Data Privacy plugin of the BMC Compuware Topaz Workbench. Before submitting an extract request with the DPR data privacy option, you must have defined the Dynamic Privacy Rules Project using BMC Compuware File-AID Data Privacy. |
3 | No Disguise. The extracted data will not be disguised. |
DCF: Control File
Specify the name of Disguise Control File that contains the disguise criteria for this extract. Required for Disguise Selection option 1. Disguise Control Files can be created in Option 5, Data Disguise (refer to Allocate Disguise Control File). The disguise criteria is specified using Option 5, Data Disguise (see 1 - Criteria).
Hints
- Before you submit the disguise job, make sure that the Disguise Control File includes the desired disguise criteria for the objects included in the extract file.
- It is also recommended that the relationship information in both the extract and Disguise Control File matches.
- Also, when using disguise rules with complex criteria, the object that you used to define the criteria originally must be included (not excluded) in the extract file or the disguise may not be successful.
- For related disguise rules, always define the criteria on the object that contains all of the different unique values (including orphans) to be extracted.
DPR: Repository Name
Specify the name of the Privacy Rules Repository to be used with Disguise Selection option 2 for this extract.
Specify the full repository name (up to 128 characters). Or enter an asterisk (*) by itself for a list of all repositories. Then select the desired repository from the list (see Privacy Repository List).
This field is prefilled with your current profile’s value (see DPR: Repository Name) or global default value (see Option G—Global User Defaults).
DPR: Project Name
Specify the name of the Dynamic Privacy Rules Project to be used with Disguise Selection option 2 for this extract. Dynamic Privacy Rules are created with the BMC Compuware File-AID Data Privacy component of the BMC Compuware Topaz Workbench. The Dynamic Privacy Rules Project keeps track of how to apply the privacy rules to which extracted data element. This option requires installation of Compuware’s BMC Compuware File-AID/Data Solutions and BMC Compuware File-AID Data Privacy.
Specify the full project name (up to 128 characters) or a pattern ending with an asterisk (*) for a list of matching projects. Asterisk (*) by itself lists all projects. Then select the desired project from the list (see Privacy Project List).
This field is prefilled with your current profile’s value (see DPR: Project Name).
Retain pre-disguise file
Specify whether or not to retain the extract work file before data is disguised. The extract work file is always in a masked format to prevent access to the undisguised data.
Yes | Retain the extract work file before data is disguised. |
No | Don’t retain the extract work file before data is disguised. |
The extract and the disguise are run as separate job steps. By saving the undisguised file you can rerun the disguise without having to rerun the extract. The disguise may need to be rerun because it failed due to an error in the disguise criteria, insufficient unique replacement values or because the disguise criteria did not produce the expected results. To rerun a failed disguise, use Option 5.2, DCF: Disguise Existing Extract.
The name assigned to the pre-disguise extract file will use the standard RDX routine to generate a "temporary" name. The name will be the user PREFIX, the mid-level qualifier from the Profile, the word "EXTRACT" and finally the current date and time fields (i.e. D050128.T055709).
Create Audit Trail
Specify whether or not the BMC Compuware File-AID/Data Solutions disguise process should produce an audit trail report for each object whose data is subject to be disguised.
Yes | Create audit trail reports using BMC Compuware File-AID/Data Solutions audit trail exits. Note that the BMC Compuware File-AID/Data Solutions audit trail exits determine if a report is created and what is reported. |
No | Don’t create audit trail reports. |
Audit Trail file prefix
Specify the prefix for the BMC Compuware File-AID/Data Solutions audit trail reports for this extract. Prefix plus USERID can be up to 14 positions, the remainder of the data set name will follow the above mentioned naming convention. If prefix is blank, only the USERID will be used. Any value specified will be appended to the USERID. Precede the prefix value with a single quote (‘) to use the value without the USERID.
Related topics