This topic describes how to configure a skin. If you want to configure a skin that was previously disabled, before you begin, select the Show Disabled checkbox (next to the Maintain option in the Groups menu).
The following tables describe each option on the various sections of the Group Configuration screen. Update the desired options then click the Save button.
| Option | Description |
|---|---|
|
Group Name |
This field displays the group name. |
| Description | This field displays the group description, which was defined when the group was created. |
| Company Name and Company Address | Address information can be found in the contract (stored on the SharePoint site). The company name and address are displayed in email notifications. The company address displays in the consent text. |
| Context ID | This field displays the Context ID number for the group |
|
Maximum Number of Web Service Recipients |
Leave the number set to 5, which is the maximum numbers of recipients per package. |
|
Disable Sent By Heading |
Select this checkbox to remove the "Sent by" heading from the consumer site document list. |
|
Allow HTML Content |
Select this checkbox to allow HTML content in packages. |
|
Use Paper Status in Compliance Search Results |
Need definition |
|
Use Skin Holiday Dates |
Select this checkbox to use the holiday dates configured in the skin. If this checkbox is left clear, the default holiday dates will be used. |
|
Enable Push Notifications |
Select this checkbox to enable the ability to push a status via XML to the customer’s front-end system. If this option is selected, the user account that is sending the package must be configured for it to work properly. INSERT HYPERLINK TO CONFIGURATION DETAILS |
|
Use First Notification |
Select this checkbox if the customer is using the auto-create on the fly method of new user registration when sending packages to recipients. Result: Accounts are created and an initial notification is sent to recipients before sending packages. What (if any) other options need to be configured to use this "on the fly" method, or is this the only thing? It seems pretty important and the option title is not intuitive, so getting the explanation right here will be valuable. What is the default setting? |
|
Warn On No Attachments |
Select this checkbox to warn the sender when no attachment has been attached to the package. |
|
Show eConsent For All Packages |
need info |
|
Use Morvision Mapping |
When this checkbox is selected and SDX Capture is attached to the skin, SDX automatically maps the "LoanID" and "BorrowerID" fields into "Loan Number" and "Borrower Name" via the getConfig web service call. |
|
Allows Check Recipients Before Sending |
Select this checkbox to enable a function in SDX to always check if the recipient is currently registered before sending packages. |
|
Use Web Form Creation |
This checkbox is for Sun Trust only. Select this checkbox to allow users to send web forms in the user site. |
|
Allow Smart Consent |
Select this checkbox to enable Smart Consent functionality, which enables you to provide consent at a user level instead of on a package-by-package basis. Choosing this option allows a one-time consent, which then applies to all future packages until you elect to opt out. If SmartConsent is enabled, then packages will not expire to paper unless you decide to opt out or decline SmartConsent. Reviewer note: do we need to explain why packages do not expire to paper? Also: The configuration settings that become enabled when "Allow Smart Consent" is checked are not explained. What is the default setting? |
| Option | Description |
|---|---|
|
Home Page Logo URL |
URL for the customer logo on the Home page. Reviewer Notes: need clarification - Is this the Home Page for the User Site or the Consumer Site, or both? Do we need to explain why this needs to be a URL (rather than a loaded image)? Are there any restirctions on what type of graphic file this needs to be? Where should the logo (ideally) be located e.g. in a particular location on the installation server? Are there any restrictions or recommendations on file size and/or physical pixel dimensions? |
|
Logo URL |
URL for the customer logo that displays in the upper left corner of consumer pages (after login). Do we need to explain why this needs to be a URL (rather than a loaded image)? Are there any restirctions on what type of graphic file this needs to be? Where should the logo (ideally) be located e.g. in a particular location on the installation server? Are there any restrictions or recommendations on file size and/or physical pixel dimensions? |
|
Home Page Colours |
These fields contain RGB color codes for the Login page. The first field controls the border color. The second field controls the screen color. Click the buttons to display a color palette. Click to select a color from the palette. The code for the color you select displays in the field. NOTE: Color should be American spelling. Make sure verbiage is consistent with what is on configuration page. Where should the SysAdmin get this colour information from? How will the Customer communicate their colour requirements? What are the default settings, so that something acceptable can be recovered if a colour selection error is made? |
|
Login Colours |
These fields contain RGB color codes for the consumer pages (after login). The first field controls the border color. The second field controls the screen color. Click the buttons to display a color palette. Click to select a color from the palette. The code for the color you select displays in the field. Reviewer Note: According to the configuration page, it also sets the colours for the User site pages. And it refers specifically to it being the colours of the Login Page, rather than "after login". Which is correct? |
| Option | Description |
|---|---|
|
Create Package Text |
The meta data variables to display in email notifications, subject headers, and reports. |
|
Subject Meta Data |
The list of available meta data items. REVIEW NOTE: would it be useful to explain to the SysAdmin how to set up the meta data items? Make sure the guide includes details of the default settings for these fields. "Typical" settings for each one would also be useful, where a default is not available. |
|
Subject Meta Data To View |
The list of items to display in user’s mail boxes in SDX (Inbox, Sent Items, and so on). |
|
Subject Meta Data for Web Forms |
This field is for web form users only. The list of subject meta data items for web forms. |
|
Subject Meta Default Data for Web Forms |
This field is for web form users only. The list of items to display in user’s mail boxes in SDX (Inbox, Sent Items, and so on) for web forms. |
|
Subject Meta Data to Report |
The list of items to display in the SDX Admin report. |
|
Subject Meta Data in Notifications |
The list of items to display in the email notifications sent to recipients. |
|
Subject Meta Data in Notification Subject Item |
The meta data item to display in the notification subject header. |
|
Subject Meta Map to Subject Item |
The meta data item to display in the subject headers of other email templates. This option allows specific meta data items to be mapped to the subject field within a message. Typically, this value would be set to comment. |
|
Subject Meta Data Dynamic Items in Body |
The list of items that can be used in the email template in addition to the standard meta data items in the templates. |
|
Subject Meta Data Dynamic Items in Subject Line |
The meta data items to display within the subject of a package template |
|
Subject Meta Data Password Field |
This field is for users who use an item from the meta data as their password. |
|
View Subject Notification |
The list of items to display in the subject of the view notification. |
|
Masked Subject Meta Data with Count |
This field is used for partially masking sensitive information in the meta data such as account numbers or Social Security Numbers. Specify the number of characters at the end of the specified data that will be shown - all other preceding characters will be masked with asterisks e.g. account number=3:ssn=4 This will show the last 3 and 4 characters of account number and ssn respectively. The other characters will be masked. |
|
Mask Subject in Reports |
Select the checkbox to partially mask sensitive information such as account numbers or Social Security Numbers in the Subject line for reports. By default, this setting is enabled. |
| Option | Description |
|---|---|
|
Include Subject Meta Map to Subject in Reports |
Select this checkbox to include the subject meta data in reports. review note: Why would/wouldn't you do this? Some examples would be helpful. What is the default setting? |
|
Filter out subject in meta data |
Select this checkbox to set meta data items into separate nodes on the web service call. review note: Why would/wouldn't you do this? Some examples would be helpful. What is the default setting? earlier comment: This field should in initial caps |
| Option | Description |
|---|---|
|
Extract User's Name from Meta Data |
Enter the subject meta data for the user's first and last name. reviewer note: Who would have created the metadata tags? How would I find the list of available fields? |
| Option | Description |
|---|---|
|
Meta Data for Custom Templates |
The most common meta data items are Loan Number and Borrower Name. The availability of other meta data items is subject to the SDX delivery method chosen by the customer. For Example, eDisclosures sent from SDX Capture can only use the meta data items completed on the screen when sending an eDisclosure package. Streamlined implementations always utilize the Loan Number, Borrower Name and Comment fields for all subject meta data. reviewer note: How will I know which SDX delivery method the customer has chosen? Where will I find this? |
| Option | Description |
|---|---|
|
Multiple Question Authentication Enabled |
Select this checkbox to enable authentication. reviewer note: This is now broken out in to to checkboxes - standard (?) and web forms When do these questions appear? E.g. when the user signs in? when they change their password? If multiple places, are all controlled by the same configuration checkbox, or are any non-configurable e.g. always on? |
|
Subject Meta Data Authentication Questions & Answers |
Enter the challenge questions in the Subject Meta Data Authentication Questions & Answers field. reviewer note: It would be useful of the inline help/examples that is available on the form itself were also duplicated here. How many question/answer pairs can be supported? |
|
Challenge Answer Page Wording |
Enter the wording to display on the challenge answer page. For example: Please answer the following questions. |
|
No of Authentication Answers Required |
Enter the number of authentication answers required by the user before they can access their SDX package. For example: There may be 4 challenge questions entered in the Subject Meta Data Authentication Questions & Answers field yet you can enter 2 in this field. In this case, using the 4 questions, SDX randomly presents them to the user one-by-one until 2 correct answers are given. This field should be "Number" reviewer notes: What happens if authentication questions are enabled but this field is set to zero? Does the system keep repeating questions indefinitely until the user gets the specified number of answers correct? If not, what is the limit? e.g. 4 questions have been set, Answers required is set to 2, the user answers the first three questions incorrectly... do we ask the final question even though they now can't get two answers correct (assuming each question can only be answered once), or do we re-present a "fifth" question from the remaining 3 that have so far not been answered correctly? Presumably "randomly" actually means randomly selected from the remaining unanswered questions? Or can the user be presented with the same question twice?? |
|
Lock User when Incorrectly Answer Challenge Questions |
Select this checkbox to lock the account of a user when they incorrectly answer their challenge questions. Is this one wrong answer or does it depend on how many questions and required answers? Example: If there are 4 questions and 3 required answers, will the account be locked after 1 wrong answer or 3? Also: Missing information: Some details needed around this check box. Note that the default setting seems to be "enabled" Presumably in line with the rules defined above e.g. if they have been presented with all the available questions and have not been achieved the "No of Authentication Answers Required" number. Should we include a warning that if the "No of Authentication Answers Required" is greater than the number of question/answer pairs, the user could get locked out without getting anything wrong? Or do we check this internally before accepting the completed form? |
| Allow Challenge Questions Request in User Site | Check this box to display the challenge questions on the user site for users to enter answers to the challenge questions prior to viewing their package. reviewer note: Presumably this is in addition to the challenge questions on sign in, if that option is also enabled? Or is this actually the place where the user sets the answers to their challenge questions? Not really clear - can't see how that would be a separate configuration item, when obviously if question authentication is enabled above they will have to enter answers to those questions somewhere? |
| Option | Description |
|---|---|
|
Authentication on Non eDisclosures Enabled |
eDisclosure packages always require challenge questions. Select this checkbox to enable challenge question authentication for all non eDisclosure packages. Essentially, when this option is selected, all packages will require challenge question answers. Examples of non eDisclosure packages are an appraisal package sent to a borrower recipient or a closing package sent to a title company recipient. reviewer note: How is this possible if the options above have not been selected to enable setting of questions answers? How does the system determine whether a package is an eDisclosure or not? Is this configured for each package when the package is created and sent? |
|
Non eDisclosure Authentication Meta Data Item |
If the checkbox above is selected, enter ‘closing’ in this field. reviewer note: What does that mean/do? What is entered if the checkbox above is not selelcted? Are there really not any other options? |
|
Non eDisc Meta Data Value Reqd |
<<<Need description >>> "Required:" should be spelled out, perhaps "eDisclosure" should be, too. |
| Option | Description |
|---|---|
|
Paper Out Account Address |
Enter the paperout@wolterskluwer.com address for customers who are implementing paper fulfilment with their SDX implementation. Customers can also implement their own paper fulfilment process, although this is rarely done. |
|
Hide Paper Out Button |
Select this checkbox to disable the Request Paper button on the message screen so the recipient cannot request a package to be printed and mailed to them. This option should remain selected to prevent paper out customers from sending a hard-copy package when the recipient views it electronically. |
|
Send Declined (not consented) packages to Paper |
Select this checkbox to send declined packages to the paperout account to be papered. reviewer note: Additional note on the configuration page states "This is for non workflow packages" - what does this mean? What hapens with "workflow packages"? |
| Option | Description |
|---|---|
|
On Package Error Account Send Email |
Select none, one, or any combination of the checkboxes, then add the appropriate email addresses to receive package error messages. If desired, in the first field, enter the SDX Support address: sdxsupport@wolterskluwer.com reviewer note: Not completely consistent with what the checkboxes actually suggest - in two of the cases, not only an email but the actual Package is sent e.g. "Send Package to Sender". Is this what actually happens? What is the reason for sending the Package? Does this mean the SysAdmin needs to be particularly careful about the email address entered in the third option (for compliance reasons)? What does "if desired" relly mean? How will the SysAdmin know whether to use the SDX Support address or not, where do they fond this information? Config page includes "The user must exist in this skin. Email address does not require the context id" - needs further explanation |
| Option | Description |
|---|---|
|
Use Lib Docs |
Select the checkbox to include the HUD, CHARM, Interest Only and HELOC booklets with the eDisclosure package. If you select this option, enter LIBDOCS in the Lib Docs Field Name field. reviewer note: What are the consequences of selecting this checkbox and not entering LIBDOCS in the field name? Are there any other field name options? |
|
LibDoc Mandatory Files |
To filter which booklets are sent, enter the booklets in filename.pdf format. Example: Enter "Charm.pdf,HELOC.pdf." In this case, only the CHARM and HELOC booklets are included in the eDisclosure package. reviewer note: So if nothing is entered here, no booklets are included, even if the checkbox above is selected? Is there a list of all the available booklets? Are there others in addition to those listed in the guidance above? Is this field case sensitive? |
| Option | Description |
|---|---|
|
Site Url |
Enter the URL for all pilot QuickSkin sites. Note: The True URL for the site is listed under the Site URL. Bookmark and send the True URL to the customer. The True URL contains a unique context number that identifies the site for each customer. Reviewer note: Why only for the pilot site? What happens to this URL once the site moves beyond pilot? Do SysAdmins need this pilot site version/info, or is there something more appropriate?Reviewers: Is this acurrate????? Comments said the site URL contains the unique number. Not sure if I have this right. Bookmark For what purpose? Knowing this might help the SysAdmin to send it at the most appropriate time, rather than just at the point that they are configuring this information. |
|
Help Desk Name |
Enter the name of the Help Desk contact to display on the SDX screens and notifications. This should always be Wolters Kluwer Financial Services for streamline implementations. reviewer note - Give an example of what name to use for non-streamline implementations? How does the SysAdmin know which to use? |
|
Help Desk Number |
Enter a phone number for the Help Desk contact that displays on SDX screens and notifications. For streamline implementations, use Wolters Kluwer Financial Services' SDX support toll-free number. For the pilot site, use 111-111-1111 as customers should contact their Implementation Consultant during the implementation phase. reviewer note: Although it does appear to be the default setting on the config page, it might be helpful to include it here also, in case the SysAdmin has deleted it by mistake. |
|
Help Desk Email Address |
Enter the email address for the Help Desk contact that displays on the SDX screens and notifications. This should be sdxsupport@wolterskluwer.com. |
|
Help Desk Hours |
Enter the support hours for the Help Desk contact that displays on the SDX screens and notifications. Use the exact wording as you wish the support hours to display, such as: 8:00am-8:00pm EST. reviewer note: Include the default WK hours here, in case they have been deleted from the config page but are needed again. |
| Option | Description |
|---|---|
| Product Content Support Name | Enter the name of the contact for questions on package contents. This name displays within the SDX site screens and notifications. This support name should be the customer's company name or customer service. |
| Product Content Support Number | Enter the phone number for questions on package content. This number displays on SDX site screens and notifications. The content support phone number should be the customer's customer service number or contact information, such as "your loan officer." |
| Option | Description |
|---|---|
| Notify From | Enter the SDX email address used to send packages and from which the notification emails originate. This address is the customer's preferred name with the @secury-dx.com |
| Use Display Name | Check this box to allow the client to use the same send by address when sending a package. reviewer note: should this be "allow the client to use the display name"? |
| Display Name | Enter the name to be used as the display name. |
| Reply to Sender for Emails | Check this box to enable notifications to be sent from the Notify From email address. This box should be checked for streamline implementations. |
| Reply to Address for Emails |
If Reply to Sender for Emails is disabled, enter the reply to address here. reviewer note: What will happen if the box is unchecked but no email address is added here? |
| Option | Description |
|---|---|
| Send Emails to Recipient | Check the appropriate box(es) to send an email to the recipient for any of the following events:
|
| Send Emails to Sender | Check the appropriate box(es) to send an email to the sender for any of the following events:
|
| Option | Description |
|---|---|
| Reply By Fax | Check this box to enable the Reply by Fax functionality for both Senders and Recipients. |
| Fax Number | Enter the fax number for the Reply by Fax functionality. |
| Option | Description |
|---|---|
| Self Registration | Check this box to enable self registration functionality. Doing so enables the "I am a new user" link on the SDX homepage. New users may then click that link to register on the SDX site. This self registration method includes an approval process by the customer. |
| Approver Email | Enter the email address for the staff member who is assigned to approve self-registered users. |
| Disable Employers Name Field | Check this box to disable the employer name field from displaying on the new user registration screen. reviewer note: Some info on when/why this might be necessary would be helpful. |
| Option | Description |
|---|---|
| Allowed Suffixes | Use this field to enter any domain suffixes allowed to send packages to external email addresses. The organization's main domain suffix and any other suffix used by the organization must be listed in this field. When listing suffixes, use the comma (,) to separate items in the list. |
| Option | Description |
|---|---|
| Location Checking | Use this function to restrict where users can enter the site - either by IP or by suffix. reviewer note: Does this mean "restrict access to the user site"? |
| User/Consumer Site | Use these checkboxes to restrict the user and consumer site by checking one or more of the following options:
reviewer note: There seems to be a place to put the list of restricted IP addresses, but where are the restricted suffixes configured? Is this the same list of Allowed Suffixes that are allowed to send packages to external email addresses? What does Allow Login on No Match mean? If this is unchecked, is login prevented altogether? Who receives the warning emails? |
| Admin Site | Use these checkboxes to restrict the user and customer site by checking one or more of the following options:
reviewer note: There seems to be a place to put the list of restricted IP addresses, but where are the restricted suffixes configured? Is this the same list of Allowed Suffixes that are allowed to send packages to external email addresses? What does Allow Login on No Match mean? If this is unchecked, is login prevented altogether? Who receives the warning emails? |
| IP Address(es) | Enter allowed IP addresses as an example below. reviewer note: No example actually given. Whose IP address is this likely to be, where does this IP address come from? |
| Option | Description |
|---|---|
| Use Consumer Skin | Check this box to allow the use of the consumer skin. reviewer note: Needs more info. Under what circumstances would the customer not want to use a consumer skin? What happens if this is checked/unchecked? |
| Enable Consumer Skin Reply | Check this box to allow the consumer to reply in the consumer skin. reviewer note: Examples of when this would/wouldn't be beneficial would be useful. |
| Show Papered Packages in Message List | Check this box to allow the listing of packages which have gone to paper to display in the consumers inbox. reviewer note: Could we give an example of a time when we wouldn't want to do this? How does the SysAdmin make a decision about these things, is it detailed in the customer contract? |
| Show Notice of Package having gone to Paper | Check this box to display within the consumer site inbox which packages have gone to paper. reviewer note: What is tha actual difference between this and the previous check box - needs to be clearer. What is the most common way to configure (both/neither/one or the other)? |
| Option | Description |
|---|---|
| Use Random Initial Password | Check this box to issue a random password to new users. Doing so disables the standard password setting below. reviewer note: Presumably an email message is always triggered when a new user is created, either with a random password (if configured here) or with the set password. It might be useful if this process was clarified (although maybe not here!) |
| Create User Password | Enter a standard password to be sent to users when they are created. reviewer password: Should this standard password conform to the password policy that is subsequently provided (if only as a good example)? Is it checked? |
| Password Policy Regex | Enter the Regex code specific for the SDX default password, containing letters and numbers, with at least 6 characters, but no more than 10 characters. For streamline implementations, this default should NOT be changed. This Regex code can be changed to accommodate other password requirements for max/min length, upper/lower case, special characters, etc. reviewer note: Will a SysAdmin always know what Regex means? Should we explain? Would be useful to include this default value somewhere in the Admin Guide, in case it does get removed by accident and/or we decide to remove the comment from the Group Config page in the future. Can we link to guidelines for Regex codes? Or at least provide the syntax? |
| Password Policy Alert | Enter the alert language to display on a popup window when the password policy has not been followed by the user. reviewer note: Is this text usually defined by the customer? Where will the SysAdmin find it? How many chars are allowed? |
| Minimum Previous Passwords | Enter a the minimum number of previous passwords before a password may be reused. This setting prevents the reuse of previous passwords. reviewer note: Is there a max number that can be entered here? What is recommended? How will the SysAdmin know what the customer wants? |
| Locked Account Alert | Check this box to alert when a user tries to log in to a locked account on either the consumer or user site. reviewer notes: Who is alerted? How are they alerted? Is this text usually defined by the customer? Where will the SysAdmin find it? How many chars are allowed? |
| Locked Account Popup Text | Enter the text to be used as the alert verbiage when the Locked Account Alert checkbox is enabled. reviewer note: Is there a max number of chars that can/should be entered here? Does the customer provide this text? |
| Locked Account Personal Reset | Check this box to allow users to reset their accounts via generated email to the user's primary email address with a link to unlock the account. |
| Option | Description |
|---|---|
| Use Proof of Reader | Check this box to check if the recipient's computer has the Adobe reader software necessary to view the PDF packages. When checked, users with the Adobe reader software are presented with the Proof of Reader page prior to viewing the package. reviewer note: What happens if this box is unchecked but the recipient does have Adobe Reader - will they see the Proof of Reader page or not? |
| Option | Description |
|---|---|
| Digitally Sign PDFs | Check this box to enable the digital signature functionality within SDX. When this functionality is enabled, the package received by the recipient must be SIGNED or REJECTED after the PDFs are viewed. reviewer note: If this is disabled, can recipients still opt to sign digitally if they wish, or is it simply not available? |
| Allow eSign Request In User Site | reviewer note: What does this do? Is it so the user can request to digitally sign if the checkbox above is disabled? |
| Custom Digital Signature Placement - Textbox name | Enter the name to apply to the signature on the PDF. review note: An example would be useful, not clear what this should be. Is there a min/max number of chars? Can it include special chars? |
| Custom Digital Signature Placement - Digital Signature field name | Enter the field name for the signature box where the signature is placed. review note: An example would be useful, not clear what this should be. Is there a min/max number of chars? Can it include special chars? |
| Option | Description |
|---|---|
| Show Group Name When Signing | Check this box if you wish to have the Group Name display in the popup as the receiver of the signed package. review note: Who/what will be shown as the receiver if this box is not checked? |
| Option | Description |
|---|---|
| Show Legal and Letter PDF versions | review note: no information provided. |
| Option | Description |
|---|---|
| Watermark Consented PDFs | Check this box to have the consented watermark appear on the package documents after the I Consent button is clicked during package retrieval. Note: If documents are to be digitally signed, this watermark field should remain unchecked. review note: is consented the same as signed? what happens if this is enabled when docs are digitally signed? |
| Watermark Text Enabled | Check this box to enable the watermark text in the text box to print for the consented or signed watermarks. The watermark text, length, angle, font size, and page position can also be changed.
review note: Refers to "consented or signed" but checkbox above only seems to pertain to consented. Which is correct? Does length mean number of characters or physical size on the page? |
| Date Text Enabled | Date\By Font Size field review note: These are actually two separate config items so should be described separately. It should be clarified that enabling "Date Text" in fact includes both Date Signed and Who Signed. |
| Watermark Footnote Enabled | Check this box to specify having the watermark print in the document footer rather than across the page. The footnote text, length, font size, and date/by font size all function the same way as the watermark text.
review note: is it possible to enable both? |
| Option | Description |
|---|---|
| Send Welcome Package | Check this box to enable sending of the standard SDX welcome package. This is a standard package not sent out by Wolters Kluwer. This box should always remain unchecked. review note: Presumably this means that it should be left unchecked at the top level, but that customers might want to enable this at the individual group levels? |
| Welcome Package Sender | This field is used to list the email address for the sender of the welcome packages. This field should always remain blank. review note: Always remain blank at the top level, for configuration in the customer's individual groups? |
| Welcome Package Attachment | This field is used to add an attachment to the package when it is sent to a new user. review note: If this were being used, is this a link to the file on the customer's own server? |
| Option | Description |
|---|---|
| Client Legal Text | Use this field to enter the wording for the link at the bottom of the login page to link to a client site or legal documentation. review note: It would be useful to also include the advise text from the configurtion page e.g. Include http:// or https:// before the URL e.g. http://www.isentry.com |
| Client Legal Link | Use this field to enter the link for the legal text defined in the previous field. |
| Option | Description |
|---|---|
| Login Page Verbiage | Use this field to enter custom text for the login page. This text should be plain text only and should not contain hyperlinks. review note: Is there a limit on the number of chars or recommneded number of chars? Where on the Login Page does this appear? Include the comment |
| Option | Description |
|---|---|
| Legal Notice to New Users | Use this field to enter any legal text for your users to guide them when entering their user information. For example, use legal name. review note: Where does this information get displayed? How many chars? Any restrictions? |
| Option | Description |
|---|---|
| Enable Inactive Users Report | Check this box to enable functionality that will allow reports to be run on inactive users. |
| Inactive Days | Enter the number of days a user must be inactive before being categorized as an inactive user and included in reporting. |
| Restricted Suffixes | Enter any suffixes to which the report should be limited. The report will return just the suffixes entered in this field. Separate suffixes with a comma ( , ). review comment: Include examples, as per the config page. Is there any limit on how many suffixes? |
| Exclude Locked Accounts | Check this box to exclude locked accounts from being run and included within the report. |
| Option | Description |
|---|---|
| Enable Pagination | Check this box to enable the ability to set the number of packages to be shown on a page within the user's inbox. |
| Pagination Message Count | Enter a number to specify the number of packages to be shown. |
| Option | Description |
|---|---|
| Authentication Engine URL | info needed |
| Authentication Engine Username | info needed |
| Authentication Engine Password | info needed |
| Option | Description |
|---|---|
| Feedback Email | Enter the address to which a user can send feedback about the site.
review notes: Additional information needed about the check boxes - presumably these refer to where the feedback link is available. |
| Option | Description |
|---|---|
| Custom eSign note | Check this box to enable the use of a custom alert to display when a user e-signs a package. Then, enter the custom text in the text field. review note: Is it the user who sees this alert? Does it allow them to change their mind or is it purely informational? |
| Custom Rejection Message | Check this box to enable the use of a custom alert to display when a user rejects a package. then, enter the custom text in the text field. review note: Is it the user who sees this alert? Does it allow them to change their mind or is it purely informational? |
| Option | Description |
|---|---|
| Enable Courier Labeling | Exclusive for Veteran United. Check this box to allow the skin to create a courier label. |
| Meta Data Trigger Field | Enter a value in this field to be used in the subject line with the DOCTYPE meta data item. For example, sending a package with DOCTYPE=predisclosure sets the package as one that allows a user to create a courier label in the consumer site. |
| Web End Point | Enter the URL for the web service that is required to create the label. |
| Web Auth Key | Enter the client's FedEx Web Authentication Key required to create a FedEx label. |
| First Name Meta Item | Enter the meta data item used to get the recipient's first name. |
| Mailing Address Meta Item | |
| Send To Address ( | Delimited) | Enter the address to be shown on the label. |
| Send To Company Name | Enter the company name to be shown on the label. |
| Send To Support Line | This error message displays if an error occurs while rendering the label. |
| Account No. | Enter the client's FedEx account number, which is required to create a FedEx label. |
| Meter No. | Enter the client's FedEx meter number, which is required to create a FedEx label. |
| Web Auth Password | Enter the client's FedEx Web Authentication Password, which is required to create a FedEx label. |
| Last Name Meta Item | Enter the meta data item used to get the recipient's last name. |
| Phone Number Meta Item | Enter the meta data item used to get the recipient's phone number. |
| Label Text | Enter the REF: value to be used on the label. |
| Send To Phone Number | |
| Courier Required Meta Items (; delimited) |
| Option | Description |
|---|---|
| QS Information/Error Alerts | Use this field to list the email address to be used to send error text when an error has occurred while creating a FedEx label. review note: It's not clear… does this apply to all accounts, or is it a continuation of the above Veteran United exclusive? There is no other mention of FedEx labels in the configuration. |
| Option | Description |
|---|---|
| Last Changed | This field displays the last date the skin configuration was changed. |
| Last Changed By | This field displays the email address for the last person to change the skin configuration. |
| Last Change Description | This field displays a list of which values were most recently changed and saved. |