| TITLE | EMBEDDERS | AUTHOR | LINK |
|---|---|---|---|
| Introduction to Salesforce Sales Cloud | YouTube | Salesforce | click here "" |
| Salesforce for marketing | YouTube | Salesforce | click here "" |
| Salesforce for customer service | YouTube | Salesforce | click here "" |
| Salesforce for sales | YouTube | Salesforce | click here "" |
| Convert profile permissions to permission sets with Salesforce Helper APP | YouTube | Salesforce | click here "" |
Leonard STRONG. All rights reserved.
---------------------
---------------------
---------------------
User profiles have access to several types of licenses, including :
- Salesforce" licences for "internal" CRM users such as sales teams
- Salesforce Platform" licences for "partner" CRM users such as business teams or partners
- Customer Portal" licences for users linked to contacts
To manage the rights of users linked to contacts, the procedure is as follows
- Create the user from the contact, for each contact concerned
- Create a "customer" profile to which these "customer" users will be associated, using the "Customer Portal" licence type
- Create a "platform" profile to which the "business" or partner users will be associated, using the "Salesforce Platform" licence type
Once all the expected user profiles have been created:
- Enter the community settings area
- Open the Administration screen, then "Members".
- Select the profiles by filtering on the type of licence (customer, internal, partner or all)
Sites are set in the configuration area (configuration -> Sites and domains -> Sites).
A site can be a community, communities are also set up in the configuration area (configuration -> Communities -> All communities
When creating: define the label and name
When creating and modifying: define the contact and the different pages and control parameters.
The components of a community are added in the workspace generator.
| TITLE | PRICE | CATEGORIES | FIRST RELEASE | LIGHTNING READY | MOBILITY | PREREQUISITE |
|---|---|---|---|---|---|---|
| Social Hiring and Applicant tracking system | From 69.99 USD / user / month | Human Resources | 11 July 2014 | yes | not | |
| TheHRMS Human Resource Management system | Contact us | Human Resources | 19 February 2014 | not | not | |
| Jobscience | 160 USD / user / month | Human Resources | 14 September 2007 | not | yes |
| TITLE | PRICE | CATEGORIES | FIRST RELEASE | LIGHTNING READY | MOBILITY | PREREQUISITE |
|---|---|---|---|---|---|---|
| Free of charge | Campaign Management | 22 January 2014 | yes | not | ||
| LinkedIn Sales Navigator for Salesforce | Free of charge | Productivity | 13 January 1900 | yes | not | |
| Viadeo for Salesforce | Free of charge | Sales Intelligence | 12 October 2011 | not | not |
| TITLE | PRICE | CATEGORIES | FIRST RELEASE | LIGHTNING READY | MOBILITY | PREREQUISITE |
|---|---|---|---|---|---|---|
| Salesforce CPQ | From 75 EUR / user / month | Quotes & Orders | 21 April 2010 | yes | yes | |
| Free CPQ Solution | Free of charge | Quotes & Orders | 30 November 2015 | not | not |
| TITLE | PRICE | CATEGORIES | FIRST RELEASE | LIGHTNING READY | MOBILITY | PREREQUISITE |
|---|---|---|---|---|---|---|
| Microsoft Dynamics NAV | From 250 USD / subscription / month | Integration | 14 March 2007 | yes | not | |
| Sage Business Cloud Financials | From 549 USD / Company / month | Accounting | 12 August 2015 | yes | not | |
| Invoices for Salesforce | From 59 USD / user / month | Accounting | 31 January 2012 | yes | yes | "Efficient invoicing/billing and receivables right within Salesforce Your invoices are already in Salesforce, however scattered across customers and sales records. So invoicing should simply involve automatically piecing these parts together, without re-keying a thing. This is what Invoices for Salesforce does. Simple!" |
| TITLE | PRICE | CATEGORIES | FIRST RELEASE | LIGHTNING READY | MOBILITY | PREREQUISITE |
|---|---|---|---|---|---|---|
| DocuSign for Salesforce | From 12 USD / user / month | Contract Management | 7 March 2010 | yes | yes | - Send, eSign & track agreements & approvals anytime, anywhere, & from any device - Grow your business efficiently by digitizing legal documents, sales agreements, HR forms, & more. |
| Adobe Sign | Free of charge | Contract Management | 6 October 2006 | yes | yes | No account or license required for e-signers -- accounts / licenses only required for senders. |
| Simple Signature | Free of charge | Contract Management | 26 May 2016 | yes | yes | -- |
| TITLE | PRICE | CATEGORIES | FIRST RELEASE | LIGHTNING READY | MOBILITY | PREREQUISITE |
|---|---|---|---|---|---|---|
| SPRINTER Agile Scrum Project Management | From 100 USD / Company / month | Project Management | 20 August 2013 | not | not | This App uses Salesforce Workflow and API that are standard features of Enterprise, Unlimited, and Developer Editions. Chatter allows users to follow and collaborate on SPRINTER items, but is not required for the App. |
| Agile Accelerator | Free of charge | Project Management | 31 March 2015 | yes | not | -- |
| Taskfeed | 25 EUR / user / month | Project Management | 23 July 2014 | yes | yes | Taskfeed required Chatter to be enabled. |
| Salesforce & JIRA Server Connector | From 10 USD / 10 licences / year | IT Management | 2 May 2008 | not | not | -- |
| TITLE | PRICE | CATEGORIES | FIRST RELEASE | LIGHTNING READY | MOBILITY | PREREQUISITE |
|---|---|---|---|---|---|---|
| MailChimp for Salesforce | Free of charge | Mass Emails | 10 July 2013 | yes | not | If you have enabled the built-in integration with salesforce.com within MailChimp you may risk adversely high salesforce.com API call volumes when used in conjunction with MailChimp for Salesforce. |
| Inxmail Professional email marketing for Salesforce | Contact us | Mass Emails | 3 January 2012 | yes | not | You need the following components to use Inxmail Professional for Salesforce CRM: Inxmail Professional ASP service/server software (licence), version 4.4.0.912 or higher; Inxmail Professional client software (optional for extended range of functions). |
| TITLE | PRICE | CATEGORIES | FIRST RELEASE | LIGHTNING READY | MOBILITY | PREREQUISITE |
|---|---|---|---|---|---|---|
| Alfresco Content Connector | Contact us | Document Management | 23 February 2017 | yes | not | In addition to this managed package, a working Alfresco environment is required, with the Content Connector for Salesforce components (amps) installed. |
| Dropbox for Salesforce | Free of charge | Collaboration | 15 October 2014 | yes | not | -- |
| TITLE | PRICE | CATEGORIES | FIRST RELEASE | LIGHTNING READY | MOBILITY | PREREQUISITE |
|---|---|---|---|---|---|---|
| Cap Adresse - Data Quality Application | Free of charge | Data Cleansing | 19 November 2014 | yes | not | |
| Clean Suite for CRM: All-in-One Data Cleansing App | 19.99 USD / Company (one time) | Data Cleansing | 3 March 2015 | yes | not | "Validate, update, enrich & dedupe your contact data *FREE TRIAL AVAILABLE* The #1 Dirty Data Fighter - Melissa's Clean Suite verifies, cleans, updates, and enriches your data. With real-time processing + batch processing available, every name, address, email and phone - will be accurate and reliable." |
| AddressTools Premium: Global Address Validation and Standardization Suite | From 900 USD / Company / year | Data Cleansing | 20 April 2010 | yes | not | For configuration options please visit the CountryComplete Administration tab after the package has been installed. |
| AddressTools Free: Address Validation and Standardization Suite | Free of charge | Data Cleansing | 15 July 2009 | not | not | For configuration options please visit the CountryComplete Administration tab after the package has been installed. |
| Opti-Time Cloud Tour | From 15 EUR / user / month | Field Service | 21 November 2014 | yes | yes |
Salesforce allows to do several Salesforce actions directly from the user's email without being connected to the application: create a Salesforce record, log an email, create a task ...
The Chrome extension for Salesforce can be downloaded from this link: https: //chrome.google.com/webstore/detail/salesforce/jjghhkepijgakdammjldcbnjehfkfmha?hl=fr. This URL corresponds to the "Salesforce Connector for GSuite" extension. The extension can also be found in the Chrome extension search box.
Once the extension has been installed, the link between the email account and the user account for the desired Salesforce environment must be configured. As a reminder, the production access URL is different from the Sandboxes access URL.
You must first enter and validate the URL for accessing the Salesforce instance (steps 1 and 2) and then identify yourself on Salesforce (step 3) to associate the email account and the user account
|
|
|
|
|
|
Use of the site implies full acceptance of the general conditions of use described below. These conditions of use may be modified or supplemented at any time, and users of the site are therefore invited to consult them regularly.
This site is normally accessible to users at all times. However, Leonard STRONG may decide to interrupt the site for technical maintenance purposes and will endeavour to inform users in advance of the dates and times of the intervention.
The site is regularly updated by Léonard STRONG. Similarly, the legal notices may be modified at any time: they are nevertheless binding on the user, who is invited to refer to them as often as possible in order to read them.
The site uses JavaScript technology.
The website cannot be held responsible for any material damage related to the use of the site. Furthermore, the user of the site undertakes to access the site using recent, virus-free equipment and with a last-generation updated browser.
Léonard STRONG is the owner of the intellectual property rights on its creations accessible on the site, in particular the texts, images, graphics, photographs, icons, sounds and software. The logos or icons of the organisations or companies mentioned on this site are the intellectual property of the organisations or companies in question.
Any reproduction, representation, modification, publication, adaptation of all or part of the elements of the site, whatever the means or process used, is prohibited, except with the prior written authorisation of : Léonard STRONG or their owner.
Any unauthorised use of the site or of any of the elements it contains will be considered as constituting an infringement and will be prosecuted in accordance with the provisions of articles L.335-2 et seq. of the Intellectual Property Code.
Léonard STRONG cannot be held responsible for direct and indirect damage caused to the user's equipment when accessing the Leonard STRONG site, and resulting either from the use of equipment that does not meet the specifications indicated in point 4, or from the appearance of a bug or an incompatibility.
Leonard STRONG may not be held responsible for indirect damage (such as loss of market or loss of opportunity) resulting from the use of this site.
Interactive areas (possibility of asking questions in the contact area) are available to users. Léonard STRONG reserves the right to delete, without prior notice, any content posted in this area that contravenes the legislation applicable in France, in particular the provisions relating to data protection. Where applicable, Léonard STRONG also reserves the right to hold the user civilly and/or criminally liable, particularly in the event of messages of a racist, insulting, defamatory or pornographic nature, whatever the medium used (text, photographs, etc.).
This site uses cookies and plugins to obtain statistics on visits over the last two weeks of activity: information on the computer used by the visitor (IP address, operating system, web browser, country of origin) is collected.
This site also has a contact form and a Multiple Choice Questionnaire on Salesforce for which authentication is mandatory with the identity and e-mail address of the person using the said elements. Reporting on the MCQ also provides an overall score for each visitor completing it.
The management of information collected for visit statistics will be reviewed in hindsight, in the short term all data is retained.
The data collected by the forms are only accessible by Léonard STRONG, the site owner. You have the possibility to request the deletion of this data.
According to the terms of the RGPD, which came into force on 25 May 2018, any person filling in the questionnaire has the right to request access to and deletion of data concerning him or her.
The Léonard STRONG site contains a certain number of hypertext links to other sites, set up with the authorisation of Léonard STRONG. However, Léonard STRONG does not have the possibility of checking the content of the sites thus visited, and consequently cannot assume any responsibility for them.
Browsing the Leonard STRONG site may result in the installation of cookie(s) on the user's computer. A cookie is a small file which does not allow the user to be identified, but which records information relating to the navigation of a computer on a site. The data obtained in this way is intended to facilitate subsequent navigation on the site, and is also intended to allow various measures of frequentation. The list of cookies is available from the dedicated link.
Refusal to install a cookie may make it impossible to access certain services. However, the user can configure his computer in the following way to refuse the installation of cookies:
The site is not declared to the CNIL because it does not use personal data as indicated on this page.
The databases are protected by the provisions of the law of 1 July 1998 transposing the directive 96/9 of 11 March 1996 on the legal protection of databases.
Any dispute relating to the use of the Leonard STRONG website is subject to French law. The competent courts of Paris have exclusive jurisdiction.
Law n° 78-17 of 6 January 1978, notably modified by Law n° 2004-801 of 6 August 2004 on information technology, files and freedoms.
Law n° 2004-575 of 21 June 2004 for confidence in the digital economy.
Regulation (EU) 2016/679 of 27 April 2016 on the protection of individuals with regard to the processing of personal data and on the free movement of such data. To access the European text, click here "".
User: Internet user connecting to and using the above-mentioned site.
Personal information: "information which allows, in any form whatsoever, directly or not, the identification of the natural persons to whom it applies" (article 4 of law n° 78-17 of 6 January 1978).
| Types of objects | Description |
|---|---|
| Standard objects | Objects included with Salesforce |
| Customised objects | Objects created by administrators to store company-specific information |
| External objects | Objects similar to Custom Objects, except that they are mapped to data outside the Salesforce organisation |
Broadcast | Year | Theme | OrgaCode | Organization |
|---|---|---|---|---|
| Europa | 1956 | Construction of Europe. Tower formed from the Latin word Europe "EUROPA". | CECA | European Coal and Steel Community |
| Europa | 1957 | Peace and prosperity through agriculture and industry | CECA | European Coal and Steel Community |
| Europa | 1958 | Peace in the service of European ideas. Dove flying over the E of Europe | CECA | European Coal and Steel Community |
| Europa | 1959 | 6-ring chain | CECA | European Coal and Steel Community |
| Europa | 1960 | 1st issue of the European Conference of Postal and Telecommunications Administrations (CEPT). Roman 19-spoke chariot wheel | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1961 | Stylized dove composed of 19 doves | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1962 | Stylized tree with 19 leaves | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1963 | United Europe. Stylized cross composed of 4 interlaced U's | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1964 | 5th anniversary of the CEPT. 22-petalled flower | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1965 | 3-leafed sprig (representing post, telephone and telegraph) and fruit composed of the letters CEPT | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1966 | Sailboat | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1967 | 22-tooth gears | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1968 | Key | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1969 | 10th anniversary of the CEPT. Ancient temple with the words Europa and CEPT as columns | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1970 | 24-wire mesh | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1971 | Chain with one link forming the O in the word Europa | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1972 | Telecommunication. Aurora Borealis composed of 14 stars | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1973 | Post, telephone and telegraph. Post horn with 3 arrows | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1974 | Sculptures | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1975 | Paintings | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1976 | Handicrafts | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1977 | Landscapes | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1978 | Monuments | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1979 | Postal history | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1980 | Famous people | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1981 | Folklore and festivals | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1982 | Historical events | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1983 | Human genius | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1984 | 25th anniversary of the CEPT - common ground: a bridge | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1985 | Music (European Year of Music) | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1986 | Nature conservation | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1987 | Modern architecture | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1988 | Transport and communications | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1989 | Children's games | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1990 | Postal buildings | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1991 | Europe and space | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1992 | 500th anniversary of the discovery of America | CEPT | European Conference of Postal and Telecommunications Administrations |
| Europa | 1993 | Contemporary art | PostEurop | Association of European Public Postal Operators |
| Europa | 1994 | Great discoveries | PostEurop | Association of European Public Postal Operators |
| Europa | 1995 | Peace and Freedom - 50th anniversary of the end of World War II | PostEurop | Association of European Public Postal Operators |
| Europa | 1996 | Famous European women | PostEurop | Association of European Public Postal Operators |
| Europa | 1997 | Tales and legends | PostEurop | Association of European Public Postal Operators |
| Europa | 1998 | National festivals and celebrations | PostEurop | Association of European Public Postal Operators |
| Europa | 1999 | Nature reserves and parks | PostEurop | Association of European Public Postal Operators |
| Europa | 2000 | New millennium - common motif: 6-star tower built by children | PostEurop | Association of European Public Postal Operators |
| Europa | 2001 | Water as a natural resource | PostEurop | Association of European Public Postal Operators |
| Europa | 2002 | The circus | PostEurop | Association of European Public Postal Operators |
| Europa | 2003 | The art of the poster | PostEurop | Association of European Public Postal Operators |
| Europa | 2004 | The holidays | PostEurop | Association of European Public Postal Operators |
| Europa | 2005 | Gastronomy | PostEurop | Association of European Public Postal Operators |
| Europa | 2006 | Integration as seen by young people | PostEurop | Association of European Public Postal Operators |
| Europa | 2007 | Centenary of Scouting | PostEurop | Association of European Public Postal Operators |
| Europa | 2008 | Correspondence: rediscovering the pleasure of writing | PostEurop | Association of European Public Postal Operators |
| Europa | 2009 | Astronomy (International Year of Astronomy) | PostEurop | Association of European Public Postal Operators |
| Europa | 2010 | Children's books | PostEurop | Association of European Public Postal Operators |
| Europa | 2011 | Forests (International Year of Forests) | PostEurop | Association of European Public Postal Operators |
| Europa | 2012 | Visit ... (e.g. "Visit France") | PostEurop | Association of European Public Postal Operators |
| Europa | 2013 | Postal vehicles (20th anniversary of PostEurop) | PostEurop | Association of European Public Postal Operators |
| Europa | 2014 | National musical instruments | PostEurop | Association of European Public Postal Operators |
| Europa | 2015 | Antique toys | PostEurop | Association of European Public Postal Operators |
| Europa | 2016 | Ecology in Europe "think green" - common motif (60th anniversary of Europa stamps) | PostEurop | Association of European Public Postal Operators |
| Europa | 2017 | The castles | PostEurop | Association of European Public Postal Operators |
| Europa | 2018 | Bridges | PostEurop | Association of European Public Postal Operators |
| Europa | 2019 | National birds | PostEurop | Association of European Public Postal Operators |
| Europa | 2020 | The old postal routes | PostEurop | Association of European Public Postal Operators |
| Form | Subform | Description |
|---|---|---|
| general collection | geographic collection | Geographical or traditional collecting consists of collecting stamps or other postal marks by country. One can specialise in certain countries. |
| specialized collection | historic collection | A collection of stamps or postal objects relating to a special period in the postal history of a country. |
| specialized collection | monographic collection | Collection of commonly used stamps to study unusual presentations, manufacturing features, varieties etc. |
| specialized collection | thematic collection | Gathering of stamps that are related to a particular theme and then organizing them for public display or preservation for encyclopedic purposes |
| Class | Subclass | Description |
|---|---|---|
| Chronological | Classic stamps | Old stamps issued before 1870 |
| Chronological | Semi-modern stamps | Stamps issued between 1870 and 1914 |
| Chronological | Modern stamps | Stamps issued from 1940 onwards |
| Type of programme | Current issue | Postage stamps printed in very large quantities for a specific purpose: franking of inner letters and postcards or as a complementary value |
| Type of programme | Special broadcast | Grouping of thematic stamps and commemorative stamps. The former are regular, the latter are not. |
| Type of programme | Common or joint issue | Stamp issues carried out in the same year by at least two countries. Most of them are one-offs between a handful of postal administrations, some are regular between member countries of the same organisation, such as the Europa issue since 1956. |
| Type of issue | Thematic stamps | Stamps illustrating a particular theme : Fauna, Flora, Jewellery etc... |
| Type of issue | Commemorative stamps | Postage stamp with a figure commemorating or illustrating a fact, a character or an event in a specific way |
| Type of issue | Tax stamps | Mark or figurine intended to prove that a citizen has paid certain categories of taxes to a public authority |
| Type of issue | Custom stamps | Postage stamps illustrated or accompanied by a vignette illustrated by a drawing or photograph chosen by an individual, association or non-governmental company. |
For more details on custom field types see the Salesforce publication, click here ""
| Type (French wording) | Type (English wording) | Type (French wording) | Type (English wording) | |
|---|---|---|---|---|
| Automatic number | Auto Number | Check box | Checkbox | |
| Currency | Currency | Date | Date | |
| Date/Time | Date/Time | Messaging | ||
| External reference relationship | External Lookup Relationship | Formula | Formula | |
| Geolocation | Geolocation | Hierarchical relationship | Hierarchical Relationship | |
| Indirect reference relationship | Indirect Lookup Relationship | Research relationship | Lookup Relationship | |
| Principal-Detail Relationship | Master-Detail Relationship | Digital | Number | |
| Percentage | Percent | Telephone | Phone | |
| Selection list | Picklist | Selection list (multiple selection) | Picklist (Multi-select) | |
| Summary of accumulation | Roll-Up Summary | Text | Text | |
| Text (encrypted) | Text (Encrypted) | Text box | Text Area | |
| Text box (long) | Text Area (Long) | Text box (enriched) | Text Area (Rich) | |
| Time | Time | URL | URL |
The error message "This page layout name already exists or has already been used. Your changes have not been saved" implies that there are duplicate actions. This is the problem to be solved to close the topic.
Under Lightning the resolution procedure is described on this Salesforce publication
|
|
|
 |  |
The objective of HRCP management is to know the average life of deals reaching one of the two final statuses (signed or lost deals) within the activity of the sales teams.
 |  |
As I show above on this achievement page, I have been working on the Salesforce Classic to Lighting Experience migration project.
Following this migration we have allowed users to switch between the two versions of the tool for a period of time.
The purpose of this report is to see the list of users using this switch with the reason for the switch over the current and previous months
As part of the monitoring of the activity of the sales teams, this report is used to monitor the rate of transformation of deals with the two final statuses: signed deals and lost deals.
The "signature date" field was created by a colleague and takes the date of the first transition to "signed deal" status.
I have created a "lost date" field which takes the date of first transition to "lost business" status and a "closing date" field which takes the date of signature or the date of loss as soon as the business is in final status. These fields are not used on the case page layouts. A workflow rule populates the lost date and the closing date is a formula field.
This work required a history of all lost cases.
 |  |
Within the framework of product management, this process builder allows new products to be automatically linked to price catalogues.
Authorised users simply create the product and all the required information is copied to the corresponding entry in the price catalogues.
This process is carried out when each new product is created, and a price catalogue entry is created for the standard catalogue and the one used by HRCP with the following information:
When I arrived on the Randstad HRCP project, the first story I dealt with was to create the business history functionality to track the sales teams' current pipeline. In this context I created the following elements:
 |  |
Example of an application page for one of the user profiles
Example of an account registration page
| Non-optimised query | Optimised query |
|---|---|
| SELECT MM.ID AS ID_METER, MIM.ID AS ID_INDEX, MM.ID_ROB_REG_RES_SITE, MM.METER_NAME, MM.GUID_METER AS ADDRESS, MIM.INDEX_NAME, MIV.CURRENT_INDEX_DATE, DECODE ( RLLOV.WORDING, lov_entry_mode_index', MIV.CURRENT_INDEX_VALUE, 'lov_entry_mode_counting_consumption', MIV.CONSUMPTION, MIV.CURRENT_INDEX_VALUE ) AS LAST_INDEX_CURRENT_VALUE, ( SELECT ROB_MEA.WORD FROM RUM_OBJECT_BASE ROB_MEA WHERE MM.ID_ROB_TYPE_METER = ROB_MEA.ID ) AS TYPE_METER, ROW_NUMBER() OVER (PARTITION BY MIV.ID_INDEX ORDER BY MIV.CURRENT_INDEX_DATE DESC) RN FROM MEA_METER MM, MEA_INDEX_METER MIM, MEA_INDEX_VALUES MIV, MEA_COUNT_TYPE MTC, RUM_LINE_LIST_OF_VALUE RLLOV WHERE RLLOV.CODE_LIST = 'MODE SAISIE TYPE COMPTAGE' AND MM.ID = MIM.ID_METER AND MIM.ID = MIV.ID_INDEX AND MIM.ID_TYPE_COUNT = MTC.ID AND MTC.ID_INPUT_MODE = RLLOV.ID | SELECT MM.ID AS ID_METER, MIM.ID AS ID_INDEX, MM.ID_ROB_REG_RES_SITE, MM.METER_NAME, MM.GUID_METER AS ADDRESS, MIM.INDEX_NAME, MIV.CURRENT_INDEX_DATE, DECODE ( RLLOV.WORDING, lov_entry_mode_index', MIV.CURRENT_INDEX_VALUE, 'lov_entry_mode_counting_consumption', MIV.CONSUMPTION, MIV.CURRENT_INDEX_VALUE ) AS LAST_INDEX_CURRENT_VALUE, ( SELECT ROB_MEA.WORD FROM RUM_OBJECT_BASE ROB_MEA WHERE MM.ID_ROB_TYPE_METER = ROB_MEA.ID AND ROB_MEA.ID_TYPE_OBJECT_BASE = 67 ) AS TYPE_METER, ROW_NUMBER() OVER (PARTITION BY MIV.ID_INDEX ORDER BY MIV.CURRENT_INDEX_DATE DESC) RN FROM MEA_METER MM, MEA_INDEX_METER MIM, MEA_INDEX_VALUES MIV, MEA_COUNT_TYPE MTC, RUM_LINE_LIST_OF_VALUE RLLOV WHERE RLLOV.CODE_LIST = 'MODE SAISIE TYPE COMPTAGE' AND MM.ID = MIM.ID_METER AND MIM.ID = MIV.ID_INDEX AND MIM.ID_TYPE_COUNT = MTC.ID AND MTC.ID_INPUT_MODE = RLLOV.ID |
If you have an account on this site or have left a comment, you are entitled to request an extract file of your personal data that we have collected. This includes the data you have provided to us.
You can also request the deletion of all or part of your personal data.
This excludes any data we are obliged to retain for administrative, legal or security purposes.
Request for personal data
Please use this form to provide / delete personal data
The "EUROPA" issue is an annual joint issue of postage stamps by the European Postal Administrations.
This issue was managed by the European Coal and Steel Community (ECSC) from 1956 to 1959 and then the European Conference of Postal and Telecommunications Administrations (CEPT) from 1960 to 1992. It has been managed by theAssociation of European Public Postal Operators (PostEurop) since 1993. Since its creation in 1956, the various editions of the "EUROPA" programme have had a common theme and/or illustration.
From 1956 to 1959 the ECSC member states were Italy, France, Benelux and Germany.
| What is Philately | click here "" |
| The London forgeries | click here "" |
| The Universal Postal Union | click here "" |
| French philatelic history | click here "" |
| British Philatelic History | click here "" |
| The Philatelic History of the British Empire | click here "" |
Broadcast | Year | Theme | OrgaCode | Organization |
|---|---|---|---|---|
| Sepac | 2007 | Landscape I | SEPAC | Cooperation of Small European Postal Administrations |
| Sepac | 2009 | Landscape II | SEPAC | Cooperation of Small European Postal Administrations |
| Sepac | 2011 | Landscape III | SEPAC | Cooperation of Small European Postal Administrations |
| Sepac | 2013 | Animals | SEPAC | Cooperation of Small European Postal Administrations |
| Sepac | 2014 | Flowers | SEPAC | Cooperation of Small European Postal Administrations |
| Sepac | 2015 | Culture | SEPAC | Cooperation of Small European Postal Administrations |
| Sepac | 2016 | Seasons | SEPAC | Cooperation of Small European Postal Administrations |
| Sepac | 2017 | Crafts | SEPAC | Cooperation of Small European Postal Administrations |
| Sepac | 2018 | Spectacular views | SEPAC | Cooperation of Small European Postal Administrations |
| Sepac | 2019 | Historic houses | SEPAC | Cooperation of Small European Postal Administrations |
| Sepac | 2020 | works from national collections | SEPAC | Cooperation of Small European Postal Administrations |
| National posts | ||
|---|---|---|
| The French Post Office | FRANCE | www.laposte.fr |
| Australia Post | AUSTRALIA | auspost.com.au |
| Swiss Post | SWITZERLAND | www.post.ch |
| The British Post Office | UNITED KINGDOM | www.royalmail.com |
| Israel Post (in English) | ISRAEL | www.israelpost.co.il |
| Businesses | ||
| Yvert and Tellier | FRANCE | www.yvert.com |
| Lindner | GERMANY | www.lindner-original.fr |
| Philantology | FRANCE | www.philantologie.fr |
| Marigny Philately | FRANCE | www.marigny-philatelie.com/fr |
| Rhône Philately | FRANCE | www.rhonephilatelie.fr |
| Associations and Chambers of Representatives | ||
| Universal Postal Union | Postal operators (world) | www.upu.int |
| International Federation of Philately | Philatelic Federations | www.f-i-p.ch |
| PostEurop | Postal operators (Europe) | www.posteurop.org |
| CNEP (trade union chamber) | FRANCE | www.cnep.fr |
| FFAP (Federation of Philatelic Associations) | FRANCE | www.ffap.net |
| American Philatelic Society | USA | stamps.org |
| Vocabulary | VulgumTechus | Lexicon | vulgumtechus.com/Lexicon_of_philacy%C3%A9lie#External_links | FFAP (Federation of Philatelic Associations) | Lexicon | www.ffap.net/Philatelie/lexiquephil.php |
Utilities are shortcuts that make it easier for utilities to access data. They can be used to avoid having to search for objects (an account, an opportunity, ...), activities (tasks or events), chat items (favorites or subscriptions) or other Salesforce components.
Administrators can customise the user interface for both customised applications (as in Classic) and standard applications (unlike Classic) through "themes and brand customisation".
In Salesfoce Classic administrators could integrate the company logo instead of the Salesforce logo in custom applications. This is carried over into Lightning Experience and completed with "themes and brand customisation".
This setting, new to Lightning Experience, also allows you to set an image or a solid colour for the wallpaper.
Salesforce offers standard themes and uses them by default.
Making education easier for students whether in a classroom, home or an internship in a foreign university by removing the cumbersone methods though new learning technologies will be the main theme of E-education Without Borders Conference which will open in the capital today.
The three-day conference aims to build new strategies for the efficient delivery of e-education, focus attention on academic standards relating to e-education issues, and facilitate the establishement of a global student forum to encourage the continuation of this initiative. The conference is organised and will be conducted by students for students.
The idea was initiated by students of the Abu Dhabi Men's College and 90% of the work for organising the conference has been done by the students, agreeing to Khalid Al Falasi, a student in the college and one of the organisers.
He said yesterday the conference would give students an opportunity to achieve direct communication. "About 300 students from 47 countries will take part in the conference to discuss their ideas and present their papers on online programs and facilities worldwide" he said.
"The most significant point is that students will speak during the conference to demonstrate their views about the future of e-learning" he said.
Khamis Al Hosani, another organiser, explained that students would highlight future challenges and needs to expand online learning programmes as well as different advantages and risks of adopting such learning methods.
He pointed out that students from more than 100 colleges and universities worldwide would present papers and hold professionnal-level discussions around the anticipated impact of e-learning methodology and technology. He also announced that the confernce would present the Cancelor's, Conference and Industrial awards to the best papers offered by students.
Dr Tayeb Kamali, Director of the college was seen to give students the chance to express themselves and organise the event according to their own views.
by a staff reporter, Khaleej Times, April 21st 2001
In the early 1950s, the Emirate of Abu Dhabi was a little visited desert. The population was reduced to a few Bedouin tribes. In 1958 a Franco-British consortium discovered an offshore oil field. Exports began four years later. In the 1970s, Abu Dhabi became a major producer of petroleum. The standard of living of the population rose considerably and the country invested in transforming the desert into a green land.
In the 1960s, with the development of oil activity, the various emirates in the region became closer. The British left the region in 1968.
Nine emirates attempt to form a union, but fail to do so: Bahrain (in August 1971) and Qatar (in September 1971) become independent.
Six of the seven current emirates (Abu Dhabi, Ajman, Dubai, Fujaira, Ras Al Khaimah, Sharjah, Umm Al Qaiwan) became independent and federated on 2 December 1971. The Emirate of Ras Al Khaimah joined the union in 1972.
Since 2000, the Emirate of Dubai has turned to new resources such as free ports, new technologies and above all luxury tourism. The city of Dubai has become the economic capital of the federation.
The U.A.E. is located in the north of the Arabian Peninsula. It borders the Kingdom of Saudi Arabia (to the South with 530 km of land border) and the Sultanate of Oman (to the North and East with 450 km of border). The United Arab Emirates has coastlines on the Persian Gulf (600 km) and on the Gulf of Oman (100 km).
The Persian Gulf coastline is lined with islands and reefs. The total surface area of the country is 83,600 km2 of which 86% (67,000 km2) is in the Emirate of Abu Dhabi alone.
At the beginning of the 2000s, the city is a contrast between the modernism of the city centre (urbanised and green) and the "destitution" of the periphery (shanty towns in the desert). As in the whole country, with only 30% of nationals, the city welcomes many foreign workers (Americans, Europeans, Indians and/or Pakistanis). Two spellings are accepted in French:
Wikipedia information about the U.A.E.: en.wikipedia.org/wiki/emirates_arabes_unis
Wikipedia information about the city of Abu Dhabi: en.wikipedia.org/wiki/Abou_Dabi_(city)
<apex:page controller=”Engagement_Ctlr” showHeader=”false” sidebar=”true”>
<style>
.blockscthead .pbSubheader{
background-color: #2175D9 !important;
color: #FFB511;
}
.header{
background: #2175D9 !important;
}
.blocksct{
background: #FFFFFF !important;
}
.outputNote{
font-weight: bold !important;
text-align:left !important;
color: #2175D9 !important;
border: 2px solid #FFB511 !important;
padding: 2px;
}
.buttons{
background: #2175D9 !important;
color: white !important;
font-size: 12px !important;
height:25px !important;
vertical-align: middle !important;
align: center !important;
border: 2px solid #FFB511 !important;
}
</style>
<apex:form id=”Engagement” styleClass=”blocksct”>
<apex:pageMessages />
<apex:pageBlock Title=”Bid Intake Requirements – Sales Checklist” mode=”detail”>
<!– Define the button apearing on the footer –>
<apex:pageBlockButtons location=”bottom”>
<apex:commandButton action=”{!save}” value=”Send the form” styleClass=”buttons” />
</apex:pageBlockButtons>
<!– Define the image apearing on the header –>
<apex:outputPanel layout=”block” styleClass=”header”>
<apex:pageBlockSection >
<apex:image id=”BidIntake” url=”{!$Resource.bid_intake_form_1920x350}” width=”1000″ />
</apex:pageBlockSection>
</apex:outputPanel>
<apex:outputPanel layout=”block” styleClass=”blockscthead”>
<apex:pageBlockSection Title=”Project”>
<apex:inputField required=”true” id=”BidSupport” label=”Bid Support: ” value=”{!eng.Bid_Support__c}” />
<apex:inputField required=”true” id=”ProjectType” label=”Project Type: ” value=”{!eng.Project_Type__c}” />
</apex:pageBlockSection>
</apex:outputPanel>
<apex:outputPanel layout=”block” styleClass=”blockscthead”>
<apex:pageBlockSection Title=”Your contact Information”>
<apex:inputField required=”true” id=”ContactName” label=”Your name: ” value=”{!eng.RUS_Team_Member__c}” />
<apex:inputField required=”true” id=”ContactEmail” label=”Your email: ” value=”{!eng.RUS_Team_Member_Email__c}” />
<apex:inputField required=”true” id=”Phone” label=”Phone: ” value=”{!eng.Contact_Number__c}” />
<apex:inputField required=”true” id=”OpCo” label=”OpCo/Concept: ” value=”{!eng.OpCoConcept__c}” />
<apex:inputField required=”true” id=”Scope” label=”Scope: ” value=”{!eng.Scope__c}” />
<apex:inputField required=”true” id=”Country” label=”Country: ” value=”{!eng.Country__c}” />
<apex:inputField required=”true” id=”City” label=”City: ” value=”{!eng.City__c}” />
<apex:inputField required=”true” id=”State” label=”State/Province: ” value=”{!eng.State__c}” />
</apex:pageBlockSection>
</apex:outputPanel>
<apex:outputPanel layout=”block” styleClass=”blockscthead”>
<apex:pageBlockSection Title=”Client Information – Please complete as much information as possible”>
<apex:inputField required=”true” id=”ClientName” label=”Client Company Name: ” value=”{!eng.Lead_Company_Name__c}” />
<apex:inputField required=”false” id=”UltimateClientName” label=”Client Company Lookup:<br>Use Lookup to search company<br> <i>Leave blank if company is not found” value=”{!eng.Ultimate_Client_Name__c}” />
<apex:inputField required=”true” id=”ClientWebsite” label=”Client Website: ” value=”{!eng.Client_Website__c}” />
<apex:inputField required=”true” id=”Industry” label=”Industry: ” value=”{!eng.Client_Industry_Sector__c}” />
<apex:inputField required=”true” id=”DueDate” label=”Due Date: ” value=”{!eng.Project_Due_Date__c}” />
<apex:inputField required=”true” id=”CurrentClient” label=”Existing client relationship with Randstad: ” value=”{!eng.Current_Client__c}” />
<apex:inputField required=”true” id=”Number_of_Locations” label=”In-Scope Locations: ” value=”{!eng.Number_of_Locations__c}” />
<apex:inputField required=”true” id=”LocationNotes” label=”In-Scope Location Notes: ” value=”{!eng.Main_Locations__c}” />
<apex:inputField required=”true” id=”BusinessType” label=”Type of business this opportunity represents: ” value=”{!eng.Type_of_Business__c}” />
<apex:inputField required=”true” id=”BidOpp” label=”Bid Opportunity (client spend): ” value=”{!eng.Client_s_Collective_Spend__c}” />
<apex:inputField required=”true” id=”Bidders” label=”Number of Competitors: ” value=”{!eng.Number_of_Bidders__c}” />
<apex:inputField required=”true” id=”DesiredDeliveryModel” label=”Desired Delivery Model: ” value=”{!eng.Desired_Delivery_Model__c}” />
<apex:inputField required=”true” id=”Solution” label=”Solution: ” value=”{!eng.Solution__c}” />
<apex:inputField required=”true” id=”PricingModel” label=”Pricing model being requested: ” value=”{!eng.Rate_card_Not_to_Exceed_Mark_up_Month__c}” />
<apex:inputField required=”true” id=”SkillSets” label=”Skill Sets Required: <br><i>(select all that apply)</i>” value=”{!eng.Skill_Sets_Required__c}” />
<apex:inputField required=”true” id=”CountriesInScope” label=”Countries for delivery: <br><i>(select all that apply)</i>” value=”{!eng.Countries_and_Locations__c}” />
</apex:pageBlockSection>
</apex:outputPanel>
<apex:outputPanel layout=”block” styleClass=”blockscthead”>
<apex:pageBlockSection Title=”Preliminary Opportunity Qualification”>
<apex:outputText value=”This section is only required when project type is RFP/RFQ” styleClass=”outputNote” />
<apex:outputText />
<apex:outputText>1. The client is accessible and has a partnership mentality:</apex:outputText>
<apex:inputField required=”true” label=”” value=”{!eng.X2_Client_Accessible_Partnership__c}” />
<apex:outputText>If True, please validate with the approximate date of our last interaction regarding this opportunity. If False, please enter N/A</apex:outputText>
<apex:inputField required=”false” label=”” value=”{!eng.X2_If_True_Approximate_Pre_Engage_Date__c}” />
<apex:outputText>2. The client has a compelling reason to buy/make a change:</apex:outputText>
<apex:inputField required=”True” label=”” value=”{!eng.X3_Client_Has_Compelling_Reason__c}” />
<apex:outputText>If True, concisely enter rationale. If False, please enter N/A.</apex:outputText>
<apex:inputField required=”false” label=”” value=”{!eng.X3_If_True_Rationale_to_Buy_Change__c}” />
<apex:outputText>3. This opportunity is aligned with Randstad s core competencies:</apex:outputText>
<apex:inputField required=”True” label=”” value=”{!eng.X4_Opportunity_Aligned_Core_Competencies__c}” />
<apex:outputText>4. The business terms are acceptable (pricing, credit, legal and risk):</apex:outputText>
<apex:inputField required=”true” label=”” value=”{!eng.X5_Business_Terms_Acceptable_CLR__c}” />
<apex:outputText>5. We have been provided adequate time to respond (E.g 2 weeks):</apex:outputText>
<apex:inputField required=”true” label=”” value=”{!eng.X6_Provided_Adequate_Time_to_Respond__c}” />
</apex:pageBlockSection>
</apex:outputPanel>
<apex:outputPanel layout=”block” styleClass=”blockscthead”>
<apex:pageBlockSection Title=”Notes/Comments”>
<apex:outputText >What additional information should we know about this project?</apex:outputText>
<apex:inputTextArea required=”false” id=”comments” label=”” value=”{!eng.Comments__c}” rows=”5″ cols=”100″ />
</apex:pageBlockSection>
</apex:outputPanel>
<!– To hide the outputPanel add the parameter {rendered=”false”} after {styleClass=”blockscthead”} –>
<apex:outputPanel layout=”block” styleClass=”blockscthead”>
<apex:pageBlockSection columns=”1″ Title=”Add files to upload” id=”theBlock”>
<apex:repeat value=”{!fileList}” var=”fl”>
<apex:pageBlockSectionItem >
<apex:outputLabel >Attachment</apex:outputLabel>
<apex:inputFile value=”{!fl.body}” lang=”EN” filename=”{!fl.Name}” id=”addFile” accept=”image/*.doc,.docx,.pdf,.xls,.xlsx,.txt, .csv” filesize=”800″ size=”50″ />
</apex:pageBlockSectionItem>
</apex:repeat>
</apex:pageBlockSection>
</apex:outputPanel><br/>
<apex:outputLabel>Please before you attach, click “Add File” to add the number of files you want to upload: </apex:outputLabel>
<apex:commandButton id=”AddAtt” value=”Add File” action=”{!AddAttachs}” styleClass=”buttons”/>
</apex:pageBlock>
</apex:form>
</apex:page>
<apex:page showHeader=”false” sidebar=”true”>
<style>
.fontyel{
color: #FFB511 !important;
}
.fontgreen{
//color: #006633 !important;
color: #009900 !important;
}
.header{
background: #2175D9 !important;
}
</style>
<apex:form id=”EngagementThankYou”>
<apex:pageBlock Title=”” mode=”detail”>
<!– Define the image apearing on the header –>
<apex:outputPanel layout=”block” styleClass=”header”>
<apex:pageBlockSection >
<apex:image id=”BidIntake” url=”{!$Resource.bid_intake_form_1920x350}” width=”1000″ />
</apex:pageBlockSection>
</apex:outputPanel>
<apex:pageBlockSection columns=”1″>
<apex:outputText value=”Thank You for submitting your request to the Customer Acceleration Team!” styleClass=”fontboldblue” />
<apex:outputText value=”You have successfully submitted your request and the information will be reviewed shortly. A member of our team will be in touch with you soon. ” />
<apex:outputText />
<apex:outputText />
<apex:outputText value=”What would you like to do next?” styleClass=”fontbold” />
<apex:outputText value=”1. If you have related documents please click on the Bids and Solutions link for your region below to submit related documents.” />
</apex:pageBlockSection>
<apex:pageBlockSection columns=”1″>
<apex:outputLink styleClass=”fontyel” value=”mailto:rpg-customerintelligence-dl@randstadusa.com”>Bids and Solutions NAM</apex:outputLink>
<apex:outputLink styleClass=”fontyel” value=”mailto:ask.gcs@randstad.com”>Bids and Solutions EMEA</apex:outputLink>
<apex:outputText />
<apex:outputText />
<apex:outputText value=”2. If you have another project to submit to the Customer Acceleration Team click below.” />
<apex:outputLink styleClass=”fontyel” value=”apex/engagement” >Bid Intake Form</apex:outputLink>
</apex:pageBlockSection>
</apex:pageBlock>
</apex:form>
</apex:page>
public with sharing class Engagement_Ctlr
{
public engagement__c eng{ get; set; }
public List<Attachment> fileList{ get; set; }
public Attachment attach{ get; set; }
private final Engagement__c engagement;
public Engagement_Ctlr()
{
// Create a constructor to populate the custom object “Engagement__c” from the VisualForce Page
eng = new Engagement__c();
// Define the default values for the VisualForce Page
eng.Bid_Support__c = ‘Yes’;
eng.City__c = ”;
eng.Country__c = ”;
eng.RUS_Team_Member__c = ”;
eng.RUS_Team_Member_Email__c = ”;
// Define the default parameters for the attachments
attach = new Attachment();
fileList = new List<Attachment>();
fileList.add(attach);
}
public Engagement__c getEngagement()
{
system.debug(engagement);
return engagement;
}
public List<Attachment> getAttachments()
{
return null;
}
public PageReference AddAttachs()
{
fileList.add(new Attachment());
return null;
}
// Component used by the button “Send” to save the page
public PageReference save()
{
eng.name = eng.Lead_Company_Name__c;
INSERT eng;
if(eng != NULL) {
List<Attachment> attachments = new List<Attachment>();
for(Attachment att : fileList){
if(att.name != null && att.body != null){
// Call the function to upload Documents in the related list “Files”
save_to_file(att.name, att.body, eng.Id);
}
}
if(attachments != null){
upsert attachments;
}
}
return new PageReference(‘/apex/Engagement_ThankYou?’+attach.Id);
}
// Function called to upload the attachments in the related list “Files”
public void save_to_file(String fileName, Blob base64Data, String relation_id)
{
if (fileName != null){
ContentVersion cVersion = new ContentVersion();
cVersion.ContentLocation = ‘S’; //S-Document is in Salesforce. E-Document is outside of Salesforce. L-Document is on a Social Netork.
cVersion.PathOnClient = fileName; //File name with extention
cVersion.Origin = ‘H’;//C-Content Origin. H-Chatter Origin.
//cVersion.PublishStatus = ‘P’;
cVersion.FirstPublishLocationId = UserInfo.getUserId();
cVersion.OwnerId = UserInfo.getUserId(); //Owner of the file
cVersion.Title = fileName; //Name of the file
cVersion.SharingOption = ‘A’;
cVersion.VersionData = base64Data; //EncodingUtil.base64Decode(base64Data); //converting your binary string to Blo
Insert cVersion;
System.debug('ContentVersion: '+ cVersion.id);
Id conDocument = [SELECT ContentDocumentId
FROM ContentVersion
WHERE Id =:cVersion.Id].ContentDocumentId;
ContentDocumentLink cDocLink = new ContentDocumentLink();
cDocLink.ContentDocumentId = conDocument;//Add ContentDocumentId
// Which object do you want to relate –> add the ID of the record
cDocLink.LinkedEntityId = relation_id;
cDocLink.ShareType = 'I';
cDocLink.Visibility = 'AllUsers';
Insert cDocLink;
System.debug('cDocLink.id '+ cDocLink.id);
}
}
}
@isTest
public class Engagement_CtlrTest
{
@isTest
public static void testEngagement() {
// Bring the value of the connected user
User u = [select id, firstname, lastname, Bypass_Validation_Rules__c from user where id=:userinfo.getuserid()];
String userID = u.ID;
String userFullName = u.firstname + ‘ ‘ + u.lastname;
// Instantiate the “form” page
PageReference pgForm1 = page.Engagement;
system.debug(‘Engagement VFP: ‘+pgForm1);
Test.setCurrentPage(pgForm1);
// Instantiate the “thank you” page
PageReference pgForm2 = page.Engagement_ThankYou;
system.debug(‘Thank you VFP: ‘+pgForm2);
Test.setCurrentPage(pgForm2);
//*****************************************************
// Test of the object ” Engagement__c ”
Engagement__c testEng = new Engagement__c( name=’Test ENG’, CreatedById = String.valueOf(userID).left(15), LastModifiedById = String.valueOf(userID).left(15));
system.debug(‘testEng: ‘+testEng);
UPSERT testEng;
system.debug(‘UPSERT 1 – testEng.Id = ‘+String.valueOf(testEng.Id).left(15));
//*****************************************************
// 1st part: no data in Engagement
system.debug(‘1st part: no data in Engagement’);
ApexPages.currentPage().getParameters().put(‘id’, testEng.Id);
system.debug(‘ApexCurrentPage: ‘+ApexPages.currentPage());
system.debug(‘testEng.Id: ‘+ testEng.Id);
Engagement_Ctlr controller = new Engagement_Ctlr();
// 2nd part : detailed Engagement
system.debug(‘2nd part : detailed Engagement’);
// Section “Project”
testEng.Bid_Support__c = ‘Yes’;
testEng.Project_Type__c = ‘RFP/RFQ’;
// Section “Your contact Information”
testEng.RUS_Team_Member__c = ‘Lenny STRONG’;
testEng.RUS_Team_Member_Email__c = ‘leonard.strong@st-groupe.fr’;
testEng.Contact_Number__c = ‘(206) 201-0123456789’;
testEng.OpCoConcept__c = ‘Enterprise Group’;
testEng.City__c = ‘Seattle’;
testEng.State__c = ‘WA’;
// Section “Client Information”
testEng.Lead_Company_Name__c = ‘Test ENG’;
testEng.Client_Industry_Sector__c = ‘Consulting’;
testEng.Project_Due_Date__c = system.today();
system.debug(‘*** system.today() ***: ‘+system.today());
testEng.Number_of_Locations__c = ‘1 – 5’;
testEng.Main_Locations__c = ‘This is a location note’;
testEng.Current_Client__c = ‘Yes’;
testEng.Type_of_Business__c = ‘Renewal/Existing’;
testEng.Client_s_Collective_Spend__c = ‘1) < $1M’;
testEng.Number_of_Bidders__c = ‘5’;
testEng.Desired_Delivery_Model__c = ‘Consulting’;
testEng.Rate_card_Not_to_Exceed_Mark_up_Month__c = ‘Fixed Fee-IT Solutions’;
testEng.Skill_Sets_Required__c = ‘IT’;
// Section “Preliminary Opportunity Qualification”
testEng.X2_Client_Accessible_Partnership__c = ‘Unknown’;
testEng.X2_If_True_Approximate_Pre_Engage_Date__c = ‘N/A’;
testEng.X3_Client_Has_Compelling_Reason__c = ‘Unknown’;
testEng.X3_If_True_Rationale_to_Buy_Change__c = ‘N/A’;
testEng.X4_Opportunity_Aligned_Core_Competencies__c = ‘Unknown’;
testEng.X5_Business_Terms_Acceptable_CLR__c = ‘Unknown’;
testEng.X6_Provided_Adequate_Time_to_Respond__c = ‘Unknown’;
// Section “Add files to upload”
Attachment attach=new Attachment();
attach.Name=’Unit Test Attachment’;
Blob bodyBlob=Blob.valueOf(‘Unit Test Attachment Body’);
attach.body=bodyBlob;
attach.parentId = testEng.Id;
ID pid=Id.valueOf(attach.parentId);
UPSERT testEng;
system.debug(‘UPSERT 2 – testEng.Id = ‘+String.valueOf(testEng.Id).left(15));
controller = new Engagement_Ctlr();
//*****************************************************
Test.StartTest();
System.debug('userFullName: ' + userFullName);
PageReference pgForm3 = page.Engagement;
ApexPages.currentPage().getParameters().put('Id',String.valueOf(attach.Id));
ApexPages.currentPage().getParameters().put('Pid', String.valueOf(testEng.Id));
system.debug(ApexPages.currentPage());
Engagement_Ctlr ctrlAttach = new Engagement_Ctlr();
ctrlAttach.attach.body=bodyBlob;
ctrlAttach.attach.Name='Unit Test Attachment1′;
ctrlAttach.save_to_file(ctrlAttach.attach.Name, ctrlAttach.attach.body, attach.parentId);
ID deleteAttachmentId = attach.Id;
Test.StopTest();
//*****************************************************
controller.getEngagement();
controller.getAttachments();
controller.AddAttachs();
controller.save();
//*****************************************************
}
}
Components
Versions
Example 1: All users in the DR Grand-Ouest (one role and its subordinates).
Example 2: all Back Office users in all Regional Directorates.
-------
-------
-------
| Non-optimised query | Optimised query |
|---|---|
| SELECT MM.ID AS ID_METER, MIM.ID AS ID_INDEX, MM.ID_ROB_REG_RES_SITE, MM.METER_NAME, MM.GUID_METER AS ADDRESS, MIM.INDEX_NAME, MIV.CURRENT_INDEX_DATE, DECODE ( RLLOV.WORDING, lov_entry_mode_index', MIV.CURRENT_INDEX_VALUE, 'lov_entry_mode_counting_consumption', MIV.CONSUMPTION, MIV.CURRENT_INDEX_VALUE ) AS LAST_INDEX_CURRENT_VALUE, ( SELECT ROB_MEA.WORD FROM RUM_OBJECT_BASE ROB_MEA WHERE MM.ID_ROB_TYPE_METER = ROB_MEA.ID ) AS TYPE_METER, ROW_NUMBER() OVER (PARTITION BY MIV.ID_INDEX ORDER BY MIV.CURRENT_INDEX_DATE DESC) RN FROM MEA_METER MM, MEA_INDEX_METER MIM, MEA_INDEX_VALUES MIV, MEA_COUNT_TYPE MTC, RUM_LINE_LIST_OF_VALUE RLLOV WHERE RLLOV.CODE_LIST = 'MODE SAISIE TYPE COMPTAGE' AND MM.ID = MIM.ID_METER AND MIM.ID = MIV.ID_INDEX AND MIM.ID_TYPE_COUNT = MTC.ID AND MTC.ID_INPUT_MODE = RLLOV.ID | SELECT MM.ID AS ID_METER, MIM.ID AS ID_INDEX, MM.ID_ROB_REG_RES_SITE, MM.METER_NAME, MM.GUID_METER AS ADDRESS, MIM.INDEX_NAME, MIV.CURRENT_INDEX_DATE, DECODE ( RLLOV.WORDING, lov_entry_mode_index', MIV.CURRENT_INDEX_VALUE, 'lov_entry_mode_counting_consumption', MIV.CONSUMPTION, MIV.CURRENT_INDEX_VALUE ) AS LAST_INDEX_CURRENT_VALUE, ( SELECT ROB_MEA.WORD FROM RUM_OBJECT_BASE ROB_MEA WHERE MM.ID_ROB_TYPE_METER = ROB_MEA.ID AND ROB_MEA.ID_TYPE_OBJECT_BASE = 67 ) AS TYPE_METER, ROW_NUMBER() OVER (PARTITION BY MIV.ID_INDEX ORDER BY MIV.CURRENT_INDEX_DATE DESC) RN FROM MEA_METER MM, MEA_INDEX_METER MIM, MEA_INDEX_VALUES MIV, MEA_COUNT_TYPE MTC, RUM_LINE_LIST_OF_VALUE RLLOV WHERE RLLOV.CODE_LIST = 'MODE SAISIE TYPE COMPTAGE' AND MM.ID = MIM.ID_METER AND MIM.ID = MIV.ID_INDEX AND MIM.ID_TYPE_COUNT = MTC.ID AND MTC.ID_INPUT_MODE = RLLOV.ID |
