Efront User Guide For Administrators

eFront Connect
User Guide for Administrators

V10.1
May 21, 2018
Copyright©2018 eFront Corporation. All rights reserved. eFront believes the information in this publication
is accurate as of its publication date. The information is subject to change without notice.
No part of this publication may be reproduced, sorted in a retrieval system, or transmitted, in any form or
by any means, electronic, recording, photocopying, scanning, or otherwise, without the prior written
permission of eFront.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EFRONT CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR
A PARTICULAR PURPOSE. Use, copying, and distribution of any eFront software described in this publication
requires an applicable software license. For the most up-to-date listing of eFront product names, see
eFront Corporation Trademarks on efront.com (http://www.efront.com). All other trademarks used herein
are the property of their respective owners.
eFront Connect - User Guide for Administrators - V10.1 - May 21, 2018
Contents
1. Read before: Checklist 5
2. Preparing the eFront Connect portal application environment 6

2.1. Define document types and groups ......................................................... 7
2.2. Define notice templates ............................................................................ 13
2.3. Define the fund opportunity status .......................................................... 14
3. Populating the eFront Connect admin database 15

3.1. Importing entities (contacts, funds, investors, investor accounts) -
Excel .............................................................................................................. 16
3.1.1 About Excel entity imports ...........................................................................16
3.1.2 Prepare an eFront Connect Excel manual import ...................................16
3.1.3 Import entities into eFront Connect with Excel .........................................21
3.2. Importing entities (contacts, funds, investors, investor accounts) -
XML ................................................................................................................ 24
3.2.1 About XML entity imports .............................................................................24
3.2.2 Prepare an eFront Connect XML manual import .....................................25
3.2.3 Import entities into eFront Connect using XML .........................................32
3.3. Importing documents................................................................................. 37
3.3.1 About document imports ............................................................................37
3.3.2 Prepare an eFront Connect batch document import ............................37
3.3.3 Import a batch of documents into eFront Connect................................39
4. Managing contacts and entities 42

4.1. Define standard menus for portal contacts ........................................... 43
4.2. Define menus for specific contacts/groups of contacts ...................... 46
4.3. Monitor contact access to documents .................................................. 49
4.4. Grant portal access to contacts .............................................................. 52
4.5. Reset a contact's password ...................................................................... 58
4.6. Block a contact from accessing the portal ............................................ 59
5. Managing documents 60
5.1. Splitting documents to create per-contact reports .............................. 61
5.2. Manage document disclaimers ............................................................... 64
5.2.1 Document disclaimer properties ................................................................65
5.3. Make documents available to contacts ................................................ 67
5.4. Notify contacts of document availability ............................................... 68
5.4.1 List of merge fields - eFront Connect notices............................................71
6. Managing opportunities 73
6.1. Display opportunities to contacts ............................................................ 74
7. Managing eFront Connect portal contact activity 76

7.1. Impersonate a contact in the eFront Connect portal ......................... 77
7.2. Monitor contact requests .......................................................................... 79
7.3. Trace contact actions ............................................................................... 81
8. Customizing the eFront Connect portal 82

8.1. What eFront Connect portal elements can you customize? .............. 83
8.2. Customize the login page ......................................................................... 88
8.3. Customize the home page disclaimer .................................................... 89
8.3.1 Example - Custom home page disclaimer ...............................................90
8.4. Customize the home page ....................................................................... 91
8.4.1 Create a help page dashboard ................................................................91
8.4.2 Apply a custom home page to all portal contacts .................................99
8.4.3 Define custom help pages by user ..........................................................100
8.5. Customize the help page........................................................................ 104
8.5.1 Create a help page dashboard ..............................................................104
8.5.2 Apply a custom help page to all portal contacts .................................106
8.5.3 Define a custom help page for specific contacts .................................107
8.6. Customize the portal menu..................................................................... 111
8.6.1 Define standard menus for portal contacts............................................111
8.6.2 Define menus for specific contacts/groups of contacts ......................113
8.7. Customize the documents disclaimer ................................................... 116
8.8. Customize the branding of portal .......................................................... 117
8.8.1 Example - Custom portal ...........................................................................130
9. Index 131
1. Read before: Checklist

Before going further, we assume that:
 You have installed an eFront Cube server following installation instructions
 You have successfully tested the eFront Cube server
 You have installed both eFront Connect applications following installation instructions
 You have successfully tested both eFront Connect applications
 You have successfully tested the communication between both eFront Connect applications
 You have set up both eFront Connect applicative environments (packages, package options,
menus, etc.)
For more information, please refer to the following documents:
 eFront Connect - Architecture & Installation Guide
 Configuring eFront Connect applications
Page 5 of 133
2. Preparing the eFront Connect portal

application environment
Useful procedures
1. Define document types and groups (page 7)
2. Define notice templates (page 13)
3. Define the fund opportunity status (page 14)
Page 6 of 133
2.1. Define document types and groups

Access rights for eFront Connect documents are managed using document type. For instance, a given
contact is allowed or denied the right to consult all the call notices that relate to the fund(s) he has invested
in.
When you import documents, you must specify a type for each document within your import file.
1. Access Misc > Document types.
The list of available document types and document type groups is displayed.
2. Under Document Types, click Add.
3. Enter the name and specify if a watermark should be generated by default, for this type.
When you define a watermark for a Document type, all documents of that type are watermarked with
the name of the ad hoc investor on the portal side.
4. (Optional) Select a disclaimer and define if the disclaimer should be persistent.
Get information about document disclaimers... (page 64)
5. Click OK.
Page 7 of 133
The document type is created.
6. Create additional document types by following the same steps.
Page 8 of 133
You are now able to manage access rights by Document type at the contact level (Administration
page).
You can now import documents and reference the created types.
7. (Optional) Group document types together:
A. Under the Groups of Document Types, click Add.
B. Select the document types to include to the group.
C. Click >>>.
D. Specify the document types for which a watermark should be generated by default.
Page 9 of 133
E. Click OK.
Page 10 of 133
The Document type group is created.
Page 11 of 133
You are now able to manage access rights by Document type group at the contact level
(Administration page).
Page 12 of 133
2.2. Define notice templates
Notice templates allow you to prepare invite or document availability notifications to push to contacts.
1. Access Misc > Templates.
2. Click New.
3. Define the template name.
4. Enter the From, Cc, Bcc and Subject fields.
For the From field, you can either enter an email address (e.g. no-reply@efront.com) or an email alias
followed by an email address between the < and > signs (e.g. eFront <no-reply@efront.com>).
5. Add personal information to the notification:
A. Click the Fields drawer.
B. Drag and drop merge fields into the body of the notification.
View the list of available merge fields... (page 71)
When the notification emails are sent, the merge fields resolve to the ad hoc values for
each contact/notice.
C. Complete the body of the notification.
D. Click Save.
6. (Optional) Tick Include attachments to send attachments uploaded at the notice template level.
7. (Optional) Tick Include documents to send documents as attachments along with the notice.
8. Click Save.
The notice templates are available from the notice creation form.
Page 13 of 133
2.3. Define the fund opportunity status
Funds flagged as opportunities will be presented as such to portal contacts, from within the Opportunities
dashboard. To be able to display opportunities, you must thus create the ad hoc fund status.
1. Open Administration > Tables Administration
2. Search and open VCFUNDSTAT.
3. Click Add new line.
4. Under Code, enter 1000.
Please note that Code field needs to be set to 1000.
5. Under Description, enter the status label.
6. Enter the remaining information.
7. Click Save & Close.
8. Reload the application.
Page 14 of 133
3. Populating the eFront Connect admin

database
To be able to serve documents to investors through the eFront Connect portal application, you first need
to populate the eFront Connect admin application database with entities (contacts, funds, investors,
investor accounts) and documents.
The eFront Connect portal application database contains no business data: all information related to
entities and documents is stored on the eFront Connect admin side. Admin-to-portal transactions are
handled by Web services.
During import, all the data being imported undergo a validation step. If the data is fully compliant with the
eFront Connect schema, and only then, actual records are created in the eFront Connect admin database.
Page 15 of 133
3.1. Importing entities (contacts, funds, investors,

investor accounts) - Excel
Concepts
About Excel entity imports (page 16)
Useful procedures
1. Prepare an eFront Connect Excel manual import (page 16)
2. Import entities into eFront Connect with Excel (page 21)
3.1.1 About Excel entity imports

eFront Connect Excel imports can potentially contain information about:
 Contacts
 Funds
 Investors
 Investor Accounts
 Access rights
Excel import rules

Specific worksheet names and columns must be defined to match the eFront Connect schema.
Refer to the section Prepare an eFront Connect Excel manual import to get more information.
3.1.2 Prepare an eFront Connect Excel manual import
Refer to the sections below to build your Excel file, depending on the entities and properties you wish to
import:
 Contacts (page 17)

 ContactAddresses (page 18)
 Funds (page 18)
 Investors (page 19)
 InvestorOffices (page 19)
 InvestorAccounts (page 20)
 ContactRoles (page 20)
 DocumentAccesses (page 21)
Page 16 of 133
3.1.2.1 Excel worksheet - Contacts
Worksheet name
 Contacts
Columns
 UID
 Salutation
 Last Name
 First Name
 Company
 Language
 Email
 Email2
 Email3
 Email Salutation
 Letter Salutation
 Description
 Office
 Office2
 Fax
 Mobile
 Car Phone
 Home
 Home2
 Home Fax
 Other Tel
 Other Fax
 Manager Name
 Manager Phone
 Assistant Name
 Assistant Phone
 Default Access
Page 17 of 133
3.1.2.2 Excel worksheet - ContactAddresses
Worksheet name
 ContactAddresses
Columns
 UID
 Main
 Address Type
 Address
 Address2
 Address3
 City
 ZipCode
 State
 Country
 Phone
 Fax
3.1.2.3 Excel worksheet - Funds
Worksheet name
 Funds
Columns
 UID
 Fund
 Short Name
 Size
 Currency
 Vintage Year
 Closing Date
 Strategy
 Geography Focus
Page 18 of 133
 Address
 Address2
 Address3
 City
 ZipCode
 State
 Country
 Phone
 Fax
 Fund Overview
3.1.2.4 Excel worksheet - Investors
Worksheet name
 Investors
Columns
 UID
 Investor Name
 Currency
 Comments
3.1.2.5 Excel worksheet - InvestorOffices
Worksheet name
 InvestorOffices
Columns
 UID
 Main
 Office Name
 Address
 Address2
 Address3
Page 19 of 133
 City
 ZipCode
 State
 Country
 Phone
 Fax
3.1.2.6 Excel worksheet - InvestorAccounts
Worksheet name
 InvestorAccounts
Columns
 UID
 Investor Account
 Fund UID
 Investor UID
 First Closing Date
 Comments
3.1.2.7 Excel worksheet - ContactRoles
Worksheet name
 ContactRoles
Columns
 Investor UID
 Investor Account UID
 Contact UID
 Start Date
 End Date
 Default Access
 Comments
Page 20 of 133
3.1.2.8 Excel worksheet - DocumentAccesses
Worksheet name
 DocumentAccesses
Columns
 Investor UID
 Investor Account UID
 Contact UID
 Document Type
 Access
 Watermark
3.1.3 Import entities into eFront Connect with Excel
1. Access Misc > Imports.

The list of imports is displayed.
2. Click New.
3. Expand the Attachments drawer.
4. Upload the Excel file containing the entities to be imported.
5. Click Save.
Page 21 of 133
6. Click Launch Import.
The status of the import switches to Importing.

7. Right click the grid > Refresh.
The import is finished.
8. Open the import to check the result:
 If the import status is Error, the import has failed.
You can view the error related to the Excel import file.
Page 22 of 133
 If the import status is Imported, the import has succeeded.
9. View imported entities and related document types access.

e.g. Open > Contacts, if you have imported contacts.
Page 23 of 133
3.2. Importing entities (contacts, funds, investors,

investor accounts) - XML
Concepts
About XML entity imports (page 24)
Useful procedures
1. Prepare an eFront Connect XML manual import (page 25)
2. Import entities into eFront Connect using XML (page 32)
3.2.1 About XML entity imports

eFront Connect XML imports can potentially contain information about:
 Contacts
 Funds
 Investors
 Investor Accounts
 Access rights
XML import rules

 Each Entity Node must have a UID attribute with an Unique Identifier per entity type (Contact,
Fund, Investor, Investor Account).
 Existing information about an entity will be overridden if the UID referenced within the import
already exists in the eFront Connect admin database.
 When updating an object, the system will override a field if and only if the tag for the field has
been explicitly defined in the document, potentially with an empty value. If not defined in the
document, the field will not be overridden with an empty value. For example, if you want to
empty the Salutation field for a contact, you need to specifically include
<Salutation></Salutation> under within the Contact node.
XML Structure
<?xml version="1.0" encoding="utf-8" ?>
<!—- (c) 2018 eFront -->
<PortalInformation>
<Contacts>
<Contact UID="12345"> … </Contact>
</Contacts>
<Funds>
<Fund UID="12345"> … </Fund>
</Funds>
<Investors>
<Investor UID="12345"> … </Investor>
Page 24 of 133
</Investors>
<InvestorAccounts>
<InvestorAccount UID="12345"> … </InvestorAccount>
</InvestorAccounts>
</PortalInformation>
3.2.2 Prepare an eFront Connect XML manual import
Refer to the sections below to build your XML file, depending on the entities and properties you wish to
import:
 Contacts (page 25)

 Funds (page 27)
 Investors (page 28)
 InvestorAccounts (page 29)
 ContactRole (page 31)
 Access (page 31)
3.2.2.1 XML - Contacts
Definition
Describes contact entities.
A contact is defined by at least a:
 UID,
 First name,
 Last name,
 and an Email
Default access rights for the contact are defined in the <Access> node. <DefaultAccess> describes
the default access that will apply to all document types not explicitly defined in the
<DocumentAccesses> tag.
When defining addresses, it is recommended to flag one as the main address (<Address
main="Y"></Address>).
Possible values
 <Address main=""></Address>: Y, N
 <AddressType></AddressType>: Business, Home, Other
 <Salutation></Salutation>: Mr, Miss, Mrs, Ms, Mr & Mrs
Example
<PortalInformation>
<Contacts>
Page 25 of 133
<Contact UID="12345">
<LastName>DELLENBACH</LastName>
<FirstName>Olivier</FirstName>
<Language>English</Language>
<Communication>
<Email>odellenbach@efront.com</Email>
<Email2> </Email2>
<Email3> </Email3>
<EmailSalutation>Dear Olivier</EmailSalutation>
<LetterSalutation>Dear Olivier</LetterSalutation>
<Description> </Description>
</Communication>
<Phones>
<Office>+33149964060</Office>
<Office2>+33149964060</Office2>
<Fax>+33149964060</Fax>
<Mobile>+33149964060</Mobile>
<CarPhone>+33149964060</CarPhone>
<Home>+33149964060</Home>
<Home2>+33149964060</Home2>
<HomeFax>+33149964060</HomeFax>
<OtherTel>+33149964060</OtherTel>
<OtherFax>+33149964060</OtherFax>
<ManagerName>Peter DURAND</ManagerName>
<ManagerPhone>+33149964060</ManagerPhone>
<AssistantName>Peter DURAND</AssistantName>
<AssistantPhone>+33149964060</AssistantPhone>
</Phones>
</Contact>
<Contact UID="67890">
<Salutation>Mr</Salutation>
<LastName>SMITH</LastName>
<FirstName>Pierre</FirstName>
<Company>eFront</Company>
<Position>CEO</Position>
<Language>English</Language>
<Communication>
<Email>jsmith@efront.com</Email>
<Email2>jsmith2@efront.com</Email2>
<Email3>jsmith3@efront.com</Email3>
<EmailSalutation>Dear John</EmailSalutation>
<LetterSalutation>Dear John</LetterSalutation>
<Description>TEST DESCRIPTION</Description>
</Communication>
<Phones>
<Office>+33149964060</Office>
<Office2>+33149964060</Office2>
<Fax>+33149964060</Fax>
<Mobile>+33149964060</Mobile>
<CarPhone>+33149964060</CarPhone>
<Home>+33149964060</Home>
<Home2>+33149964060</Home2>
<HomeFax>+33149964060</HomeFax>
<OtherTel>+33149964060</OtherTel>
<OtherFax>+33149964060</OtherFax>
<ManagerName>Peter DURAND</ManagerName>
Page 26 of 133
<ManagerPhone>+33149964060</ManagerPhone>
<AssistantName>Peter DURAND</AssistantName>
<AssistantPhone>+33149964060</AssistantPhone>
</Phones>
<Addresses>
<Address main="Y">
<AddressType>Business</AddressType>
<Address>2 rue Louis David</Address>
<Address2> </Address2>
<City>Paris</City>
<ZipCode>75116</ZipCode>
<State> </State>
<Country>France</Country>
<Phone>+33149964060</Phone>
<Fax>+33149964060</Fax>
</Address>
<Address main="N">
<AddressType>Home</AddressType>
<Address>45 avenue Mozart</Address>
<City>Paris</City>
<State> </State>
<Country>France</Country>
<Phone>+33149964060</Phone>
<Fax>+33149964060</Fax>
</Address>
</Addresses>
<Access>
<DefaultAccess>Allow</DefaultAccess>
</Access>
</Contact>
</Contacts>
3.2.2.2 XML - Funds
Definition
Describes fund entities.
A fund is defined by at least a:
 UID,
 and a Name
Long description of the fund can be defined in the <FundOverview> tag.
Example
<PortalInformation>
<Funds>
<Fund UID="F-12345">
Page 27 of 133
<Fund>eFront Partners V</Fund>

<ShortName>eFront V</ShortName>
<Size>750000000</Size>
<Currency>USD</Currency>
<VintageYear>2013</VintageYear>
<ClosingDate>12-31-2014</ClosingDate>
<Strategy>PE - Venture Capital</Strategy>
<GeographyFocus>North America</GeographyFocus>
<RegisteredAddress>
<City>Paris</City>
<State> </State>
<Country>FRA - France</Country>
<Phone>+33149964060</Phone>
<Fax>+33149964060</Fax>
</RegisteredAddress>
<FundOverview>
Some Fund Description
</FundOverview>
</Fund>
</Funds>
3.2.2.3 XML - Investors
Definition
Describes investor entities.
An investor is defined by at least a:
 UID,
 and a Name
Contacts attached to an investor account can be defined in the <ContactRoles> tag. If the
<ContactRoles> tag is found, all contact roles for this investor will be replaced by the new defined
ones.
When defining offices, it is recommended to flag one as the main office (<Office
main="Y"></Office>).
Possible values
 <Office main=""></Office>: Y, N
Example
<PortalInformation>
<Investors>
<Investor UID="I-12345">
<InvestorName>John SMITH (NEW)</InvestorName>
<Currency>USD</Currency>
Page 28 of 133
<Offices>
<Office main="Y">
<OfficeName>Paris</OfficeName>
<City>Paris</City>
<State> </State>
<Phone>+33149964060</Phone>
<Fax>+33149964060</Fax>
</Office>
<Office main="N">
<OfficeName>Paris 2</OfficeName>
<Address>45 avenue Mozart</Address>
<City>Paris</City>
<State> </State>
<Phone>+33149964060</Phone>
<Fax>+33149964060</Fax>
</Office>
</Offices>
<ContactRoles>
<ContactRole UID="12345">
<StartDate>12-31-2014</StartDate>
<EndDate>12-31-2018</EndDate>
<Comments>A Contact Role Description
12345</Comments>
</ContactRole>
<StartDate></StartDate>
6789</Comments>
</ContactRole>
</ContactRoles>
</Investor>
</Investors>
3.2.2.4 XML - InvestorAccounts
Definition
Describes investor account entities.
An Investor account is defined by at least a:
 UID,
 Name,
 and a Fund (with UID)
Page 29 of 133
Contacts attached to an investor account can be defined in the <ContactRoles> tag. If the
<ContactRoles> tag is found, all contact roles for this investor will be replaced by the new defined
ones.
The fund name supplied between <Fund UID="..."></Fund> tags is not parsed.
Possible values
 <Office main=""></Office>: Y, N
Example
<PortalInformation>
<InvestorAccounts>
<InvestorAccount UID="IA-12345">
<InvestorAccount>eFront V for John
SMITH</InvestorAccount>
<Fund UID="F-12345">eFront Partners V</Fund>
<Investor UID="I-12345">John SMITH</Investor>
<FirstClosingDate>12-31-2014</FirstClosingDate>
<Comments>An Investor Description</Comments>
<ContactRoles>
12345</Comments>
</ContactRole>
<StartDate></StartDate>
6789</Comments>
<Access>
<DefaultAccess>Deny</DefaultAccess>
<DocumentAccesses>
<DocumentAccess>
<DocumentType>Capital
Call</DocumentType>
<Access>Allow</Access>
<Watermark>Y</Watermark>
</DocumentAccess>
<DocumentAccess>
<DocumentType>Financial
Statements</DocumentType>
<Access>Deny</Access>
<Watermark>N</Watermark>
</DocumentAccess>
</DocumentAccesses>
</Access>
</ContactRole>
</ContactRoles>
</InvestorAccount>
</InvestorAccounts>
Page 30 of 133
3.2.2.5 XML - ContactRole
Definition
Describes the role of a contact.
A contact role must is defined by at least a:
 UID, matching the UID of an existing contact
Default access rights for the contact are defined in the <Access> node.
<DefaultAccess> describes the default access that will apply to all document types not explicitly
defined in the <DocumentAccesses> tag.
Sample
<PortalInformation>
<Comments>A Contact RoleDescription</Comments>
<Access>
<DocumentAccesses>
<DocumentAccess>
<DocumentType>Capital Call</DocumentType>
</DocumentAccess>
<DocumentAccess>
</DocumentAccess>
</DocumentAccesses>
</Access>
</ContactRole>
3.2.2.6 XML - Access
Definition
Describes the access rights of a contact to defined document types.
<DefaultAccess> describes the default access that will apply to all document types not explicitly
defined in the <DocumentAccesses> tag.
Possible values
 <DefaultAccess></DefaultAccess>: Allow, Deny
Page 31 of 133
 <Watermark></Watermark>: Y, N
Sample
<PortalInformation>
<Comments>A Contact RoleDescription</Comments>
<Access>
<DocumentAccesses>
<DocumentAccess>
</DocumentAccess>
<DocumentAccess>
</DocumentAccess>
</DocumentAccesses>
</Access>
</ContactRole>
3.2.3 Import entities into eFront Connect using XML

Prerequisite: Your XML file contains the required information about the entities and relative accesses.
1. Access Misc > Imports.
The list of imports is displayed.
2. Click New.
3. Access the XML Document page.
Page 32 of 133
4. Paste the XML document to import into the editor.
5. Click Save.
Page 33 of 133
6. In the General page, click Launch Import.
The status of the import switches to Importing.

7. Right click the grid > Refresh.
The import is finished.
8. Open the import to check the result:
 If the import status is Error, the import has failed.
Page 34 of 133
You can view the error related to the pasted XML file
 If the import status is Imported, the import has succeeded.
9. View imported entities and related document types access.
Page 35 of 133
e.g. Open > Contacts, if you have imported contacts.
Page 36 of 133
3.3. Importing documents

Concepts
About document imports (page 37)
Useful procedures
1. Prepare an eFront Connect batch document import (page 37)
2. Import a batch of documents into eFront Connect (page 39)
3.3.1 About document imports

eFront Connect document imports are achieved through a ZIP archive, which must contain:
 An XML or Excel manifest file listing the of documents to import and their properties
 The documents themselves
Standard document formats are supported (.xls(x), .pdf, .doc(x), etc.).
3.3.2 Prepare an eFront Connect batch document import

You can create an Excel or XML Manifest (Manifest.xls(x) / Manifest.XML) i.e. the list of documents to be
imported. For the purpose of this example, we focus on an Excel manifest - but the corresponding XML
syntax is provided further below.
1. Prepare the import manifest:
A. Create a Manifest file: Manifest.xslx.
B. Open the file.
C. Define the following columns which correspond to the document properties:
All the columns are required unless otherwise specified. Please note that the column
names are case sensitive and must be in upper case.
 FILE - file name e.g. Financial_Statement_Herakles.pdf
 FUNDUID - fund UID e.g. F-510
 INVESTORACCOUNTUID - Investor Account UID e.g. IA-1121
 DOCUMENTNAME - Document name displayed in the portal
 DOCUMENTTYPE - Document Type e.g. Financial Statement
 REFERENCEDATE - (optional) Document reference date e.g. 04/12/2016
 DUEDATE - (optional) Document due date e.g. 31/12/2016
 STARTDATE - (optional) Publish Start date (document portal availability) e.g.
04/12/2016
 ENDDATE - (optional) Publish End date (document portal availability) e.g. 01/01/2017
 WATERMARK - (optional) Generate watermark for this document? (TRUE or FALSE)
 RECOMMENDED - (optional) Recommend this document to target contact? (TRUE or
FALSE)
 DRAFT - (optional) Publish the document on the portal? (TRUE or FALSE)
Page 37 of 133
D. Reference documents to-be-imported.
The equivalent manifest in XML form would read as:

<?xml version="1.0" encoding="UTF-8"?>
<PortalInformation>
<Documents>
<Document>
<File>eFront Portfolio Monitoring - DEMO -
GETPM.XLSX</File>
<FundUID>1234</FundUID>
<InvestorAccountUID>1234</InvestorAccountUID>
<DocumentName>DEMO</DocumentName>
<ReferenceDate/>
<DueDate>12-31-2014</DueDate>
<StartDate/>
<EndDate/>
<Draft>N</Draft>
</Document>
</Documents>
Please note that the following rules apply when using Manifest.xml:
 The only accepted date format is MM-DD-YYYY;
 The xml elements (tags) are case sensitive;
 The accepted values for boolean tags (e.g. <Watermark>, <Draft>) are Y and N.
E. Save the file.
2. Build the import archive:
A. Create an empty ZIP archive.
B. Include the manifest file.
Page 38 of 133
C. Include all the referenced documents.
D. Close the archive.
3.3.3 Import a batch of documents into eFront Connect

You batch import documents in the eFront Connect admin application through a ZIP archive. The archive
must contain:
 A manifest file referencing the documents and their properties (Manifest.xlsx OR
Manifest.xml)
 All the documents to be imported
1. Access Open > Documents.
2. Under the Mass Actions drawer, click Import Documents.
3. Drag and drop the ZIP archive onto the drop zone.
Page 39 of 133
The list of documents is loaded into the import wizard.
4. Click Next >>>.

5. Enter a short description to identify the batch.
6. (Optional) Enter a comment.
7. Click Import Documents.
An import batch is created.
Page 40 of 133
8. Access Open > Batches to monitor the results.

The batch status is Imported.
9. Open the new batch generated to see the documents imported.
Imported document status is draft as specified or if you have not entered a value (Manifest.xslx -
DRAFT column). You need to publish these documents (page 67) before they are available to portal
users.
Page 41 of 133
4. Managing contacts and entities

Useful procedures
1. Define standard menus for portal contacts (page 43)
2. Define menus for specific contacts/groups of contacts (page 46)
3. Monitor contact access to documents (page 49)
4. Grant portal access to contacts (page 52)
5. Reset a contact's password (page 58)
6. Block a contact from accessing the portal (page 59)
Page 42 of 133
4.1. Define standard menus for portal contacts

1. In the main application menu, click Administration > Menus.
2. Select the Connect Portal profile.
3. For each page, add an menu entry (Menus section):

A. Click Add.
B. Define the menu identifier and caption.
4. Define the target page (Menu items section):

A. Define the caption
B. Under Path or Expression, navigate to the dashboard you wish to display.
Page 43 of 133
eFront Connect standard dashboards are available in the PTL-CONNect folder.
C. Click Runtime mode.

D. Click OK.
Page 44 of 133
The menus you have defined are available to all portal contacts.
Additional menu entries can be added per contact or group of contacts (page 46), from within the
eFront Connect admin application.
Page 45 of 133
4.2. Define menus for specific contacts/groups of

contacts
In addition to standard menus, you can display additional menus to certain contacts/groups only, based on
their business profile. To do so, you first add the dashboards you want to make available to the eFront
Connect dashboard library and then assign the contacts/groups who should be able to access these
dashboards.
1. Add a dashboard to the eFront Connect dashboard library:
A. Access Misc > Dashboards.
B. Click New.
C. Enter the following properties
 UID - uniquely identifies the eFront Connect dashboard - use for imports e.g. 5678
 Dashboard - dashboard technical code e.g. BREAKDOWNS
 Dashboard Path - path to the dashboard component to add to the library e.g.
PTL-CONNect\\FrontConnect Breakdowns Dashboard
 Region - define another region than SHARED to store the dashboard into, if needed
e.g. USER(Private)
 Display name - label of the menu that will allow to open the dashboard e.g. Portfolio
Breakdowns
 Display index - order of the page in the menu items e.g. 4
D. Click Save.
2. Assign the eFront Connect dashboard to contacts or group(s) of contacts:
A. Access the Contacts & Groups page.
B. Click Add Contact(s)/Add Group(s).
C. Select the contact/group to assign the dashboard to.
D. Click OK.
Page 46 of 133
The contact/group of contacts is assigned the dashboard.
E. (Optional) Restrict the page availability by defining a Start Date and an End Date.
F. Click Save & Close.
The portal page is available to the defined contact(s)/group(s) of contacts.
Page 47 of 133
Dashboard assignment can also be managed from the perspective of a contact/group of contact(s)
Page 48 of 133
4.3. Monitor contact access to documents

You usually set up contact rights on document types when importing contact entities. These rights can be
edited at any time for an individual contact or a group of contacts.
1. Access Open > Contact.
2. Open the contact.
3. Navigate to the Administration page.
4. In the Access Rights section, set the document access rights for the contact, in this order:
A. Default access for the contact
You define if the contact is able or not able to access all documents on the portal.
B. Group-specific access rights and watermark.

The contact is able or not able to access documents, based on the selected default access.
You define if the accesses are different from the default for each group, and if a watermark
should be generated.
Page 49 of 133
If you do not explicitly define Watermark to Yes, no watermarks are generated documents
of this group.
C. Type-specific access rights and watermark

The contact is able or not able to access documents, based on the default access defined,
and possible overrides defined at group level.
You define if the accesses are different from the default, and the group accesses if defined,
for each type, and if a watermark should be generated.
If you do not explicitly define Watermark to Yes, no watermarks are generated for
this type, except if this is set at group level.
D. Click Save.
The contact access rights are defined.
Page 50 of 133
5. Navigate to the Audit Accesses page to check the contact actual accesses, sorted by fund and
document type.
6. Click Refresh to view the latest permissions for this contact.
Page 51 of 133
4.4. Grant portal access to contacts

Once contacts entities have been created on the eFront Connect admin application, you must grant
contacts with portal access. The system will generate temporary passwords for the contacts you invite to
the portal: you can then send these credentials via email or push the required information to each contact
via customized notices.
Prerequisite: You have defined notice templates if you want to push emails with temporary credentials
1. Access Open > Contacts.
2. Select the contacts to invite to the portal.
3. Either generate temporary passwords for contacts manually... :
Page 52 of 133
A. Click Grant Access.
B. Click OK.
Temporary accesses are generated for the selected contacts.
Page 53 of 133
C. Open the generated EXCEL file.
D. Send emails to individual portal contacts with their credentials.

4. ... Or push invitation notifications to contacts:
A. Select the Invitation portal template.
Page 54 of 133
B. Click Grant Access & Invite with...
C. Click OK.
Page 55 of 133
A new notice based on the selected notice template opens.
D. Click Generate Emails.

E. Click Send Emails.
Page 56 of 133
The selected contacts receive a personal invite based on the selected template or any
custom notification defined beforehand.
Page 57 of 133
4.5. Reset a contact's password

2. Open the contact.
3. Navigate to the Administration page.
4. Enter a new password.
5. Confirm.
6. Click Apply.
A new password is generated for the contact.
.
7. Click OK.
Page 58 of 133
4.6. Block a contact from accessing the portal

2. Do either of the following:
 From the contacts grid
A. Select the contact(s).
B. Click Lock Access.
The contact(s) are no longer able to access the portal.
 From a contact's page
A. Open the contact.
B. Navigate to the Administration page.
C. Set Portal Access to Locked.
D. Click Apply.
The contact is no longer able to access the portal.
3. Click OK.
4. Click Save.
Page 59 of 133
5. Managing documents
Useful procedures
1. Splitting documents to create per-contact reports (page 61)
2. Manage document disclaimers (page 64)
3. Make documents available to contacts (page 67)
4. Notify contacts of document availability (page 68)
Page 60 of 133
5.1. Splitting documents to create per-contact reports
You can split documents that contain information for several investors to generate a document per
investor. The global document content is automatically assigned to the right investor, retrieved through the
Investor Account, referenced in each page of document, using the INVESTORACCOUNT#UID tag.
1. Create a batch object:
A. Access Open > Batches.
B. Click New.
C. Enter the batch name and other information.
D. Click Save.
2. Prepare a batch to split documents by investor:

A. In the Content section, click Browse.
B. Navigate to the PDF document(s) to import and click OK.
C. Click the Split checkbox.
D. Define the document name.
You can define a name using variables, so that they are dynamically generated for each
investor. The following keywords are available:
 {FundUID}
 {FundName}
 {InvestorUID}
Page 61 of 133
 {InvestorName}
 {InvestorAccountUID}
 {InvestorAccountName}
 {ReferenceDate|<format>}
 {DueDate|<format>}
For example :
{ReferenceDate|yy-mm-dd} Capital Call for {InvestorName}
E. Select a document type.
Get information about document types... (page 7)
F. Click Save.
3. Execute the split

A. Click Launch split.
The batch closes - reopen it to view the results. If executed without an error, the status
should be Split Complete.
The documents are generated following the supplied syntax pattern and in draft status:
they are not yet available to portal users!
B. Access the Proofing page.
The Documents drawer gets available.
4. Check the results:
A. Check the number of generated documents.
B. For each document check the content scope and the linked entities (fund, investor,
Page 62 of 133
investor account).
5. Make generated documents available to portal users:

A. To publish an individual document, click the Click to VALIDATE button.
B. To publish all documents at once, navigate to the Documents page, select the documents
and click Validate.
The documents are available to portal users.
Page 63 of 133
5.2. Manage document disclaimers

You can create disclaimers for documents to force investors to comply with your confidentiality policy.
Disclaimers will pop up regardless you access documents from the home page widgets or the
Documents page. You can also define whether disclaimers are persistent or not, by document type.
1. Create a disclaimer:
A. Access Misc > Disclaimers.
B. Click New.
C. Enter the disclaimer properties.
Get information about the disclaimer properties... (page 65)
D. Design the disclaimer.
E. (Optional) Enter a description.
F. Click Save.
2. Restrict the display of the current document disclaimer to specific contacts:
A. Access the Contacts page.
B. Click Add Contact(s).
C. Select the contact to assign the disclaimer to.
D. Click OK.
The contact is assigned the disclaimer.
E. (Optional) Define start and end dates to restrain a particular contact access to this page.
F. Click Save.
3. Link the newly-created disclaimer to a document type:
A. Access Misc > Document types.
B. Open a document type.
C. Select the newly-created disclaimer.
D. (Optional) Tick One time Disclaimer to display the disclaimer only when documents of the
current type will be first opened by an investor.
E. Click OK.
F. Click Close.
Page 64 of 133
On opening documents, investors will be presented with the defined disclaimer(s), for the defined time
period.
If investors try to download several documents for which different document disclaimer types are
defined, the disclaimers will show up one after the other. 'Declined' documents will be discarded of the
generated archive.
5.2.1 Document disclaimer properties
Field Function
Page 65 of 133
UID UID of the disclaimer object

Disclaimer Technical code of the disclaimer object
Fund UID Obsolete - Not used
Title Title of the disclaimer
Copyright Copyright field of the disclaimer
Region Region to store the disclaimer into
DisclaimerType - General for 'Home page'
- Document for 'Documents' - to be refined by document type
These values are set within the CONNDISCLAIMERTYPE

(Connect/Disclaimer Type) reference table.
Page 66 of 133
5.3. Make documents available to contacts

When preparing mass document import, you can define whether documents will be flagged with the Draft
status. Such documents will not be visible on the portal, before you undraft them.
You can toggle the status of imported documents any time and show/hide them to portal users.
You can also toggle the display of individual documents (Open > Documents).
1. Access Open > Batches.
2. Open the batch object that corresponds to the import.
3. Navigate to the Documents tab.
Publish documents to the portal

1. Select the document flagged as draft (showing in red) and click Validate.
The documents are now available from within the portal, to enabled users.
Hide documents from the portal

1. Select the available documents to hide and click Draft.
The documents are now hidden to portal users.
Page 67 of 133
5.4. Notify contacts of document availability

Once documents have been imported onto the eFront Connect admin database, you can push notices to
contacts to notify new documents are available for consultation on the eFront Connect portal. You only
need to reference documents within the notice and the system is able to find the target contacts, through
the investor account reference
1. Create a notice:
A. Access Open > Notices.
B. Click New.
C. Enter the notice name.

D. Select a Notice Type.
E. Add attachments to the notice.
F. Click Save.
2. Define the target contacts:
A. Under the Batches section, click Add Batch.
B. Select the batch which reference the documents.
You can attach several batches.
C. Under the Actions section, click Assign Contacts.
Page 68 of 133
D. Click OK.
Results are available in the Emails & Documents tab.
3. (Optional) If you have not selected a notice template, define the notice:
A. Access the Email template page.
B. Enter the From, Cc, Bcc and Subject fields.
C. Click the Fields drawer.
D. Drag and drop merge fields into the body of the notification.
View the list of available merge fields... (page 71)
When the notification emails are sent, the merge fields resolve to the ad hoc values
for each contact/notice.
E. Complete the body of the notification.
F. Click Save.
4. (Optional) Define a custom notification for a conctact:
A. Access the Target page.
B. Right-click a contact > Open Details.
Page 69 of 133
C. Author the ad hoc notification for this contact.
D. Click Save.
The specific notification will be sent to the defined contact(s) in place of the notice's or the
notice template's.
5. Generate emails to be sent:
A. (Optional) Under the Actions section, tick Include Notice's attachments.
B. Click Generate Emails.
The emails are ready to be sent.
6. Push the notice to contacts:
A. Click Send Emails.
B. Click OK.
Page 70 of 133
Emails are sent to portal contacts.
5.4.1 List of merge fields - eFront Connect notices
Contact
Name Syntax
UID {$ContactUID$}
Salutation {$Salutation$}
First Name {$FirstName$}
Last Name {$LastName$}
Company {$Company$}
Email {$Email$}
Email Salutation {$EmailSalutation$}
Temporary Password {$Password$}
Page 71 of 133
Notice
Name Syntax
UID {$NoticeUID$}
Notice Name {$NoticeName$}
Reference Date {$ReferenceDate|MMMM d,yyyy$}
Due Date {$DueDate|MMMM d,yyyy$}
Send Date {$SendDate|MMMM d,yyyy$}
Description {$Description$}
Document Name {$DocumentNames$}
Misc
Name Syntax
Url {$Salutation$}
Page 72 of 133
6. Managing opportunities
Useful procedures
1. Display opportunities to contacts (page 74)
Page 73 of 133
6.1. Display opportunities to contacts

Prerequsite: You must have created a dedicated fund status (page 14)
1. Set the prospect fund to opportunity status:
A. Access Open > Funds.
B. Create or open the prospect fund, if already existing.
C. Set the fund status to the one defined for opportunities.
D. Click Save & Close.

2. Refresh data to display the newly-defined opportunity on the portal:
A. Access Open > Documents.
B. Under the Mass Actions drawer, click Update Documents Cube.
The cube is updated with the latest database data.
Page 74 of 133
The documents related to prospect funds are now available to investors, under
Opportunities.
Page 75 of 133
7. Managing eFront Connect portal

contact activity
Useful procedures
1. Impersonate a contact in the eFront Connect portal (page 77)
2. Monitor contact requests (page 79)
3. Trace contact actions (page 81)
Page 76 of 133
7.1. Impersonate a contact in the eFront Connect

portal
eFront Connect portal admin users can impersonate a contact. For instance, you may want to:
 Ensure that highly sensitive documents are displayed only to ad hoc contacts
 Double-check the rendering of the portal for a particular contact
 etc.
1. Connect to the eFront Connect portal as an administrator.
2. Click the top right-hand menu.
3. Select Impersonate.
4. Supply the email address of the contact.
5. Click Impersonate.
The session restarts under the contact's identity - access shows as Impersonated.
Page 77 of 133
The portal displays as the contact sees it: the menus, widgets as well as the content which is available
are identical.
Page 78 of 133
7.2. Monitor contact requests

You receive requests submitted by investors through the eFront Connect portal, within the eFront Connect
admin application.
1. Access Open > Requests.
Requests submitted by all the portal contacts are displayed.
2. Double-click a request.
The request content is displayed: the contact it originates from, the targeted funds, investor accounts
and the attachments submitted by the contact.
Page 79 of 133
Page 80 of 133
7.3. Trace contact actions
All actions performed by contacts within the eFront Connect portal application are logged in a dedicated
trace table, which is accessible in the eFront Connect admin application.
1. Access Open > Traces.
All traced display - a trace is generated for most actions performed within the following actions:
 Login
 Requests
 Profile/group updates
 Opening a dashboard
 Download a document
 Flag a document as favorite
 Logout
The type of action traced is reflected by the technical value under the Action column. You can also refer
to the Object short description and the Object type.
Page 81 of 133
8. Customizing the eFront Connect portal

Concepts
What eFront Connect portal elements can you customize? (page 83)
Useful procedures
1. Customize the login page (page 88)
2. Customize the disclaimer (page 89)
3. Customize the home page (page 91)
4. Customize the help page (page 104)
5. Customize the portal menu (page 111)
6. Customize the documents disclaimer(s) (page 116)
7. Customize the branding of portal (page 117)
Page 82 of 133
8.1. What eFront Connect portal elements can you

customize?
All of the following elements from the eFront Connect portal are customizable:
Login page
Page 83 of 133
Disclaimer
Home page
Page 84 of 133
Help page
Portal menus
Portal pages
Page 85 of 133
Portal branding
How do I customize the eFront Connect portal?

Out-of-the-box customization can be performed from within the eFront Connect admin application.
You customize the portal by defining custom values to user profile package options (PCKAJXCONNECT
(eFrontConnect package)).
Page 86 of 133
Some parts of the eFront Connect portal such as the login page cannot customized directly from
within the eFront Connect admin application.
Page 87 of 133
8.2. Customize the login page
When you rely on form-based authentication, it is possible to write your own ASP.NET server page (.aspx)
to define a bespoke login window.
The standard login page login.aspx is located within the website folder. The resources which are
referenced within, such as the company logo or any other file - CSS stylesheet, JS scripts, etc. - should be
added to the same folder along with the bespoke server page itself. For more information, liaise with your
eFront consultant.
Page 88 of 133
8.3. Customize the home page disclaimer
When logging onto the eFront Connect portal, contacts are presented with a disclaimer, which notifies the
legal aspects of the portal. Through this disclaimer, GPs can display warnings about the eFront Connect
portal content, the contact rights and the level of information which is provided. Several properties of this
disclaimer can be customized including the text which displays, the layout, the title, etc.
1. Create a new disclaimer:
A. Access Misc > Disclaimers.
B. Click New.
C. Enter the disclaimer properties.
Get information about the disclaimer properties... (page 65)
D. Design the disclaimer.
E. (Optional) Enter a description.
F. Click Save.
2. Restrict the display of the current document disclaimer to specific contacts:
A. Access the Contacts page.
B. Click Add Contact(s).
C. Select the contact to assign the disclaimer to.
D. Click OK.
The contact is assigned the disclaimer.
E. (Optional) Define start and end dates to restrain a particular contact access to this page.
F. Click Save.
The custom home page disclaimer will display for the ad hoc contacts and the specified time period.
Page 89 of 133
8.3.1 Example - Custom home page disclaimer
Page 90 of 133
8.4. Customize the home page
You can customize the eFront Connect portal home page and display it:
 For all portal contacts

 For specific contacts only
It is also possible define a start and an end date to manage the display of a given page across time.
Useful procedures
1. Create a custom home page (page 91)
2. Apply a custom home page across portal contacts (page 99)
3. Define a custom home page by user (page 100)
Custom home page

Show me an example... (page 99)
8.4.1 Create a help page dashboard
1. Create a new home page dashboard:

A. Access Open > Dashboard > PTL-CONNect.
B. Select the standard help dashboard (FrontConnect Home Page - Corporate).
C. Click Duplicate.
D. Enter the name of the new home page dashboard.
e.g. FrontConnect Custom Home Page.
E. Click OK.
2. Reach the Design mode:
A. Access the newly-created dashboard.
Page 91 of 133
B. Right-click the current Page label and click Page's properties.
C. Untick Hide left margin.
The Dashboard is displayed with the Cubes and the Table Charts inherited from the
standard library PORTAL DOCUMENTS.
3. Define the home page content:
Display eFront Connect documents (Portal Widgets Table Chart)

A. Select the ad hoc cube based on the documents you wish to display in the widget, for
each user:
--> Documents flagged by portal contacts as to be consulted from within the "document"
page - SESSION.FLAGGEDDOCUMENTSPORTALCUBE
--> Documents assigned to portal contacts which have not been read yet -
SESSION.UNREADDOCUMENTSPORTALCUBE
Page 92 of 133
--> Documents flagged as "Recommended" by the GP -

SESSION.RECOMMENDEDDOCUMENTSPORTALCUBE
B. Drag and drop the doc > Portal Documents > Portal Widgets to the dashboard space.
C. In Area properties, click Hide Title.
Page 93 of 133
D. In Chart properties, define the chart title and the number of rows to display.
The widget will be presented to portal users as you defined it: each contact will see the
documents he/she has flagged from the documents page.
Page 94 of 133
On first connection, contacts will see an empty widget until they start flagging
documents.
E. Repeat with other widgets.
Page 95 of 133
Display additional custom content (External HTML gadgets)

A. Drag and drop the External HTML gadget to the dashboard space.
Page 96 of 133
B. In Area properties, click Hide Title.
C. Click Edit.
D. Untick Display Title.
Define an empty title to display only the input HTML content.
Page 97 of 133
E. Define the HTML content.
F. Click Apply.
G. Click OK.
H. Click Save.
The custom home page design is done. You can define this dashboard as the default home page or
only for defined contacts.
Page 98 of 133
8.4.1.1 Example - Custom home page
8.4.2 Apply a custom home page to all portal contacts
1. Access Administration > Account > Profiles

2. Access the Connect portal profile.
3. Under the PCKAJXPORTAL (eFrontPortal) package, define the Force Home Page option to the page you
wish to display:
Use the JavaScript syntax: DASHBOARDS:[DASHBOARDLOCATION]|RUNTIME
Page 99 of 133
e.g. DASHBOARDS:[DASHBOARDLOCATION]|RUNTIME

The custom home page is displayed for all portal users, unless otherwise specified. (page 100)
8.4.3 Define custom help pages by user

1. Access Misc > Dashboards.
2. Click New.
3. Define the eFront Connect custom home page:
A. Enter the following properties:
 UID - uniquely identifies the eFront Connect dashboard e.g. 6059
 Dash - dashboard name e.g. CUSTOMHOMEPAGE
 Dashboard Path - path to the dashboard component to be displayed e.g.
PTL-CONNect\\FrontConnect Custom Home page
e.g. USER(Private)
 Display name - name of the dashboard e.g. Help ( No specific value required if you
do not include the home page in the menu)
 Display index - order of the page in the menu items e.g. 1 ( No specific value
Page 100 of 133

required if you do not include the home page in the menu)
B. Click Save.
4. Link the home page dashboard to contact(s):
D. Click OK.
Page 101 of 133

E. (Optional) Define start and end dates to restrain a particular group/contact access to this
page.
F. Click Save.
5. Define the dashboard as the eFront Connect home page for your contact(s):
A. Right click a contact/group > Open Contact/Open Group.
The contact/group page opens.
Page 102 of 133

B. Access the Administration page.

C. Under the Dashboards section, tick Home Page next to the custom home page you have
created.
If you do not tick Home page, a new menu entry will be displayed to the user.

The home page will be displayed for the assigned contact/groups.
Page 103 of 133

8.5. Customize the help page
You can customize the eFront Connect portal help page and display it:
 For all portal contacts

 For specific contacts only
It is also possible define a start and an end date to manage the display of a given page across time.
Useful procedures
1. Create a help page dashboard (page 104)
2. Apply a custom help page to all portal contacts (page 106)
3. Define a custom help page for specific contacts (page 107)
Custom help page

Show me an example... (page 106)
8.5.1 Create a help page dashboard
1. Create a new help page dashboard:

A. Access Open > Dashboard > PTL-CONNect.
B. Select the standard help dashboard (FrontConnect Help).
C. Click Duplicate.
D. Enter the name of the new help dashboard.
e.g. FrontConnect Custom Help Page.
E. Click OK.
2. Define the help page content:
A. Access the newly-created dashboard.
B. Edit the help widget text.
Page 104 of 133

C. Enter the new help page content using HTML syntax:
Wrap your text content in the following tags:

 Page title : <div class='help_title'></div>
 Help page content: <div class='help'></div>
 Help page section: <h3 class='help_section'></div>
 Clickable images using with inline JavaScript: <img id='Topic_1_img'
src='images/skin/Ocean_plusW_11.png' onclick='HideOrShow("Topic_[Digit]");'>
 Text to toggle when the image is clicked: <p style='display:none;'
id='Topic_[Digit]_text'></p>
Page 105 of 133

8.5.1.1 Example - Custom help page
8.5.2 Apply a custom help page to all portal contacts
1. Access Administration > Account > Profiles

2. Access the Connect portal profile.
3. Under the eFrontConnect package, set the Help Page option value to the dashboard you wish to
display.
Use the JavaScript syntax: DASHBOARDS.open('[DASHBOARDLOCATION]',true);

e.g. DASHBOARDS.open('PTL-CONNect\\FrontConnect Custom Help Page',true);
Page 106 of 133


The help page is displayed for all portal users, unless otherwise specified (page 107).
8.5.3 Define a custom help page for specific contacts
1. Link a help page dashboard to contact(s):

B. Click New.
C. Click Add Contact(s)/Add Group(s)
D. Select the contact/group to assign the dashboard to.
E. Click OK.
F. (Optional) Define validity dates for the contact/group.

G. Click Save.
2. Define the eFront Connect dashboard properties:
A. Access the General page.
B. Enter the following properties:
 UID - uniquely identifies the eFront Connect dashboard e.g. 6060
 Dash - dashboard name e.g. CUSTOMHELPPAGE
 Dashboard Path - path to the dashboard component to be displayed e.g.
PTL-CONNect\\FrontConnect Custom Help page
Page 107 of 133

e.g. USER(Private)
 Display name - name of the dashboard e.g. Help ( No specific value required if you
do not include the home page in the menu)
 Display index - order of the page in the menu items e.g. 1 ( No specific value
required if you do not include the help page in the menu)
C. Click Save.
3. Define the dashboard as an eFront Connect help page for your contacts:
B. Right click a contact/group > Open Contact.
The Administration contact page is displayed.
Page 108 of 133

C. Under the Dashboards section, tick Help Page next to the custom help page you have
defined.
If you do not tick Home page, a new menu entry will be displayed for this page.
Page 109 of 133

The help page will be displayed for the assigned contact/groups.
Page 110 of 133

8.6. Customize the portal menu
Customizing the portal menus means to grant specific contacts access to portal features.
The menu items which are available to a specific portal contact are assigned:
 At user profile level (page 43) - menu items are shared across all contacts
 At contact/group of contact level (page 46) - menu items defined for specific
contacts/group of contacts
8.6.1 Define standard menus for portal contacts

1. In the main application menu, click Administration > Menus.
2. Select the Connect Portal profile.
3. For each page, add an menu entry (Menus section):

A. Click Add.
B. Define the menu identifier and caption.
4. Define the target page (Menu items section):

A. Define the caption
B. Under Path or Expression, navigate to the dashboard you wish to display.
Page 111 of 133

eFront Connect standard dashboards are available in the PTL-CONNect folder.
C. Click Runtime mode.

D. Click OK.
Page 112 of 133

The menus you have defined are available to all portal contacts.
Additional menu entries can be added per contact or group of contacts (page 46), from within the
eFront Connect admin application.
8.6.2 Define menus for specific contacts/groups of contacts
In addition to standard menus, you can display additional menus to certain contacts/groups only, based on
their business profile. To do so, you first add the dashboards you want to make available to the eFront
Connect dashboard library and then assign the contacts/groups who should be able to access these
dashboards.
1. Add a dashboard to the eFront Connect dashboard library:
B. Click New.
C. Enter the following properties
 UID - uniquely identifies the eFront Connect dashboard - use for imports e.g. 5678
 Dashboard - dashboard technical code e.g. BREAKDOWNS
 Dashboard Path - path to the dashboard component to add to the library e.g.
PTL-CONNect\\FrontConnect Breakdowns Dashboard
e.g. USER(Private)
 Display name - label of the menu that will allow to open the dashboard e.g. Portfolio
Breakdowns
 Display index - order of the page in the menu items e.g. 4
D. Click Save.
2. Assign the eFront Connect dashboard to contacts or group(s) of contacts:
D. Click OK.
Page 113 of 133

E. (Optional) Restrict the page availability by defining a Start Date and an End Date.
F. Click Save & Close.
The portal page is available to the defined contact(s)/group(s) of contacts.
Page 114 of 133

Dashboard assignment can also be managed from the perspective of a contact/group of contact(s)
Page 115 of 133

8.7. Customize the documents disclaimer
Refer to the section Manage document disclaimers (page 64).
Page 116 of 133

8.8. Customize the branding of portal
eFront Connect allows you to customize numerous layout elements: colors, borders, spacing, icons, etc.
These elements can be setup in package options, at user profile level.
1. Access Administration > Account > Profiles.
2. Select the portal users' user profile (e.g. Connect Portal)
3. Access the Options page.
4. Define the following options:
Desktop & Navigation
Field Value and Example

Portal title eFront Investor Portal
Title color #0AADFF

(top)
Menu bar Left

alignment
Menu #0AADFF
backgroun
d color
Menu bar 15pt

font size
Menu bar #333333

foreground
color
Page 117 of 133

Menu bar 70
height
Menus #FFFFFF
border
color
Menus #000000
specific
border
color
Font Verdana
Family
Page 118 of 133

Top bar #066799

backgroun
d color
Top bar #0AADFF

foreground
color
Top bar 150

height
Selected #777777
Menu
backgroun
d color
Settings #333333
backgroun
d color
Page 119 of 133

Backgroun #333333
d color
Copyright 2015 eFront. All rights reserved.

text
Bottom Ticked
bar
Unticked
Bottom #333333
bar
backgroun
d color
Bottom #333333
bar
foreground
color
Dashboard & Navigation
Field Description
Dashboard selected
border color
Dashboard border
color
Dashboard border
width
Dashboard border
styles
Page 120 of 133

Dashboard tabs
Dashboard tabs
border
Dashboard tabs
spacing
Drawer closed /images/skin/Ocean_Resizer_Arrow_Left_Chrome.png

arrow (Chrome)
Define an alternative relative URL rather than overwriting the URL provided
Page 121 of 133

Drawer closed /images/skin/Ocean_Resizer_Arrow_Left.png

arrow (IE)
Page 122 of 133

Drawer open arrow /images/skin/2013_arrow_down_background_Chrome.png

(Chrome)
Page 123 of 133

Drawer open arrow /images/skin/2013_arrow_down_background.png

(IE)
Drawer font size 10pt
Drawer font weight Bold
Page 124 of 133

Drawers color #333333
Left margin #FFFFFF

background color
Page 125 of 133

Left margin color #FFFFFF
Left margin filters #FFFFFF

color
Page 126 of 133

Left margin filters #333333

scroll bars color
Left margin filters #333333

scroll color
Page 127 of 133

Left margin filters /images/ajxrep-wait10.gif

wait image
Left margin #333333
selected drawer
color
Page 128 of 133

Selected page color #777777
Page 129 of 133

8.8.1 Example - Custom portal
Page 130 of 133

9. Index
A
About document imports • 37
About Excel entity imports • 16
About XML entity imports • 24
Apply a custom help page to all portal contacts • 104, 106
Apply a custom home page to all portal contacts • 91, 99
B
Block a contact from accessing the portal • 42, 59
C
Create a help page dashboard • 91, 104
Customize the branding of portal • 82, 117
Customize the documents disclaimer • 82, 116
Customize the help page • 82, 104
Customize the home page • 82, 91
Customize the home page disclaimer • 82, 89
Customize the login page • 82, 88
Customize the portal menu • 82, 111
Customizing the eFront Connect portal • 82
D
Define a custom help page for specific contacts • 104, 107
Define custom help pages by user • 91, 100
Define document types and groups • 6, 7, 62
Define menus for specific contacts/groups of contacts • 42, 45, 46, 111, 113
Define notice templates • 6, 13
Define standard menus for portal contacts • 42, 43, 111
Define the fund opportunity status • 6, 14, 74
Display opportunities to contacts • 73, 74
Document disclaimer properties • 64, 65, 89
E
Example - Custom help page • 104, 106
Example - Custom home page • 91, 99
Example - Custom home page disclaimer • 90
Example - Custom portal • 130
Excel worksheet - ContactAddresses • 16, 18
Excel worksheet - ContactRoles • 16, 20
Excel worksheet - Contacts • 16, 17
Excel worksheet - DocumentAccesses • 16, 21
Excel worksheet - Funds • 16, 18
Excel worksheet - InvestorAccounts • 16, 20
Excel worksheet - InvestorOffices • 16, 19
Excel worksheet - Investors • 16, 19
G
Grant portal access to contacts • 42, 52
I
Impersonate a contact in the eFront Connect portal • 76, 77
Import a batch of documents into eFront Connect • 37, 39
Import entities into eFront Connect using XML • 24, 32
Import entities into eFront Connect with Excel • 16, 21
Importing documents • 37
Importing entities (contacts, funds, investors, investor accounts) - Excel • 16
Importing entities (contacts, funds, investors, investor accounts) - XML • 24
L
List of merge fields - eFront Connect notices • 13, 69, 71
M
Make documents available to contacts • 41, 60, 67
Manage document disclaimers • 7, 60, 64, 116
Managing contacts and entities • 42
Managing documents • 60
Managing eFront Connect portal contact activity • 76
Managing opportunities • 73
Monitor contact access to documents • 42, 49
Monitor contact requests • 76, 79
N
Notify contacts of document availability • 60, 68
P
Populating the eFront Connect admin database • 15
Prepare an eFront Connect batch document import • 37
Prepare an eFront Connect Excel manual import • 16
Prepare an eFront Connect XML manual import • 24, 25
Preparing the eFront Connect portal application environment • 6
R
Read before
Checklist • 5
Reset a contact's password • 42, 58
S
Splitting documents to create per-contact reports • 60, 61
T
Trace contact actions • 76, 81
W
What eFront Connect portal elements can you customize? • 82, 83
X
XML - Access • 25, 31
XML - ContactRole • 25, 31
XML - Contacts • 25
XML - Funds • 25, 27
XML - InvestorAccounts • 25, 29
XML - Investors • 25, 28

Efront User Guide For Administrators

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Efront User Guide For Administrators

Загружено:

Авторское право:

Доступные форматы

eFront Connect

User Guide for Administrators

1. Read before: Checklist 5

2. Preparing the eFront Connect portal application environment 6

3. Populating the eFront Connect admin database 15

4. Managing contacts and entities 42

5.4.1 List of merge fields - eFront Connect notices............................................71

7. Managing eFront Connect portal contact activity 76

8. Customizing the eFront Connect portal 82

1. Read before: Checklist

2. Preparing the eFront Connect portal

2.1. Define document types and groups

The document type is created.

6. Create additional document types by following the same steps.

The Document type group is created.

2.2. Define notice templates

2.3. Define the fund opportunity status

3. Populating the eFront Connect admin

3.1. Importing entities (contacts, funds, investors,

3.1.1 About Excel entity imports

Excel import rules

3.1.2 Prepare an eFront Connect Excel manual import

 Contacts (page 17)

3.1.2.1 Excel worksheet - Contacts

3.1.2.2 Excel worksheet - ContactAddresses

3.1.2.3 Excel worksheet - Funds

3.1.2.4 Excel worksheet - Investors

3.1.2.5 Excel worksheet - InvestorOffices

3.1.2.6 Excel worksheet - InvestorAccounts

3.1.2.7 Excel worksheet - ContactRoles

3.1.2.8 Excel worksheet - DocumentAccesses

3.1.3 Import entities into eFront Connect with Excel

1. Access Misc > Imports.

6. Click Launch Import.

The status of the import switches to Importing.

 If the import status is Imported, the import has succeeded.

9. View imported entities and related document types access.

3.2. Importing entities (contacts, funds, investors,

3.2.1 About XML entity imports

XML import rules

3.2.2 Prepare an eFront Connect XML manual import

 Contacts (page 25)

3.2.2.1 XML - Contacts

3.2.2.2 XML - Funds

<Fund>eFront Partners V</Fund>

3.2.2.3 XML - Investors

3.2.2.4 XML - InvestorAccounts

3.2.2.5 XML - ContactRole

3.2.2.6 XML - Access

3.2.3 Import entities into eFront Connect using XML

4. Paste the XML document to import into the editor.

6. In the General page, click Launch Import.

The status of the import switches to Importing.

 If the import status is Imported, the import has succeeded.

9. View imported entities and related document types access.

e.g. Open > Contacts, if you have imported contacts.

3.3. Importing documents

3.3.1 About document imports

3.3.2 Prepare an eFront Connect batch document import

D. Reference documents to-be-imported.

The equivalent manifest in XML form would read as:

C. Include all the referenced documents.

D. Close the archive.