B. E-mail Notification for Digital Signatures

This chapter describes how to activate, configure, and use the e-mail notification functionality for electronic signatures in UniField. It covers configuration settings, notification delays, reminder logic, signature expiration alerts, and how to access notification logs.

1. Activating the E-mail Notification Functionality

The e-mail notification module for electronic signatures is managed centrally from the Administration menu. Access requires the Sync_Config user role.

1.1 Navigating to the Configuration Screen

From the UniField main screen, go to:

AdministrationConfigurationEmailEmail Notification for Signatures Configuration

Figure 1 – UniField home screen: navigate to Administration to access e-mail notification settings.

Figure 2 – Email Notification for Signatures Configuration screen (all options inactive by default).

1.2 Configuration Settings Overview

The configuration screen is divided into three sections: global notification switches, reminder configuration, and document applicability.

Setting Description
Active Master switch. When unchecked, no e-mail notifications are sent for electronic signatures, regardless of other settings.
Delay Configurable delay before the first automatic notification is sent after a document becomes signable. Options: 15 minutes, 30 minutes (default), or 60 minutes.
Signature Expiration Reminder When checked, a reminder about approaching signature validity expiry is included in notifications and reminders when the stored e-signature is 30 days or less from its expiry date.
Send initial Email manually Shortcut button to immediately trigger a test or manual initial notification without waiting for the scheduler.
Send reminder Email manually Shortcut button to trigger a manual reminder for testing purposes.
Reminder Active Activates the daily reminder cycle. When enabled, the system sends periodic reminder e-mails to pending signees until the document is fully signed or 30 days have elapsed since the first notification.

Figure 3 – Configuration screen with Active, Signature Expiration Reminder, and Reminder Active all enabled.

1.3 Document-Level Activation

Below the global settings, the Document Applicability table lists all document types that support electronic signatures. Notifications are sent only for document types that are marked as Active in this table.

Note: By default all documents are set Inactive

Figure 4 – Document Applicability table.

2. Notification Delays and the Initial E-mail

The notification system operates through two distinct scheduled mechanisms, each with a different delay pattern. Understanding how they interact is important for setting user expectations.

2.1 First (Initial) E-mail Notification

When a document becomes signable, a configurable delay is applied before the system sends the first notification to the current signee. This delay provides a correction window: if the document is signed before the delay expires, no notification is sent at all.

There are two ways to trigger the initial notification:

Option A – Automatic (Scheduler-based)

The scheduler runs periodically and checks for documents that have been in a signable state longer than the configured delay. Once the delay has elapsed and the signature is still pending, the system automatically sends the initial notification.

Setting Description
Delay options 15 minutes / 30 minutes / 60 minutes
Grouping Notifications for the same recipient are consolidated: a single e-mail lists all documents awaiting that user’s signature.
Condition No notification is sent if the document was signed during the delay window.

Option B – Manual Trigger

Users with appropriate access can bypass the scheduler by clicking the “Send request to sign” button on the Signature tab of the document. This sends the notification immediately, without waiting for the scheduler.

  • The button is visible only when: notifications are globally active, the document type is active, all required signees are assigned, and the document is not yet fully signed.
  • Manually triggered notifications are sent per document (not consolidated into a grouped e-mail).

Figure 5 – Signature tab of a Purchase Order: the ‘Send request to sign’ button (top right) and the Email logs section at the bottom showing notification history.

ℹ Note: the manual ‘Send request to sign’ button is functional only on Purchase Orders. On other document types, the button is hidden.

2.2 Cascade Notification Logic

Notifications follow a strict cascade: only the next required signee in the sequence is notified. No “for your information” e-mails are sent to previous signees who have already acted, or to future signees whose turn has not yet been reached.

When a signee completes their signature, the cascade logic applies the same configured delay before sending the notification to the next signee in the sequence.

⚠ Important: E-mail notifications are strictly informational. They do not constitute approval, delegation, or legal signature. All signature actions must be performed within UniField directly.

2.3 Daily Reminder (Reminder Workflow)

If the Reminder Active checkbox is enabled in the configuration, a separate daily scheduler runs once per day to send reminders to signees who have not yet acted on a pending signature request.

Setting Description
Trigger Runs once per day.
Condition Initial notification must already have been sent (automatic or manual).
Duration Reminders are sent for a maximum of 30 days after the document first became signable. After 30 days, reminders stop automatically.
Grouping Reminders for the same recipient are consolidated into a single daily e-mail covering all pending documents.
Stop conditions Reminders stop when: the document is fully signed, the document is cancelled, or the 30-day window has elapsed.
ℹ Note: The 30-day reminder window is counted from the moment the document becomes signable — not from the date the initial notification was sent, and not from the signature validity expiry date.

3. Signature Expiration Reminder

UniField stores a validity period for each user’s electronic signature. The signature expiration reminder is an optional add-on that embeds an expiry alert within regular notifications and reminders, without generating a separate e-mail.

3.1 How it works

When the Signature Expiration Reminder checkbox is active in the configuration, the system checks the stored signature expiry date of each notified signee. If the expiry date is 30 days or less from today, an expiry alert line is automatically included in the same notification or reminder e-mail.

Setting Description
Activation Enabled via the ‘Signature Expiration Reminder’ checkbox in Administration → Configuration → Email → Email Notification for Signatures Configuration.
Trigger condition The stored e-signature of the notified user expires within 30 days.
Delivery The expiry message is appended to the regular notification or reminder e-mail — no separate expiry e-mail is generated.
Independence The expiry reminder is independent from the 30-day document reminder window. Expiry alerts can appear in any notification triggered by the scheduler or manually.
⚠ Important: If a user’s signature has already expired, they cannot be assigned as a signee. The system prevents selection of signees with expired validity. A notification is sent to users holding the Sign_document_creator_finance or Sign_document_creator_supply role so that renewal or reassignment can be arranged.

4. Who Receives the Notifications

Notification recipients follow the cascade logic of the electronic signature workflow. A clear set of rules governs who receives which type of e-mail.

Setting Description
Initial notification / Reminder The current required signee only — the next person in the signature sequence whose action is pending.
Cascade (next signee) The notification is sent to the next signee only after the previous one has signed, respecting the same configured delay.
Fully signed notification Sent to the document creator once the last required signature has been applied.
Expiry alert (signature expiry approaching) Included in notifications sent to the signee whose personal e-signature validity is within 30 days of expiry.
Expired signature alert (for reassignment) Sent to users with the Sign_document_creator_finance or Sign_document_creator_supply role, to allow corrective action.
ℹ Note: E-mail content is intentionally minimal: it includes only the instance name, document type, document reference, a call to action, and — if applicable — the expiry alert. No financial data, supplier names, document content, or signature history is included in the e-mail.

5. Viewing Notification Logs

Two levels of notification logging are available in UniField: per-document logs, and a global log accessible from the Tools menu.

5.1 Per-Document Log (Signature Tab)

Within any signable document, open the Signature tab and scroll to the bottom. The Email logs section lists all notifications sent for that document, showing:

  • Email recipient(s)
  • Date sent
  • Final result (e.g. “The email was sent successfully”)
  • State (Success / Error)

Figure 6 – Email logs section at the bottom of the PO Signature tab, showing the full notification history for that document.

5.2 Global E-mail Log (Tools)

A consolidated log of all signature-related e-mails sent across the instance is available at:

Tools → Email logs → Signature email logs

This logs limited to technical information only: recipient e-mail address, linked UniField user, and timestamp. No message content or delivery metadata is stored.

Figure 8 – Tools → Email logs menu, showing the Signature email logs entry alongside existing log categories.

F. LU-SU2105 Gestion des Kits : Comparer LCK et TCK

Manuel de l’Utilisateur Supply -> 3. Produits -> 3.6 LU-SU2105: Kits/Modules -> F. LU-SU2105 Gestion des Kits : Comparer LCK et TCK

1. Vue d’ensemble

La fonction Comparer LCK et TCK est un outil de reporting au sein du module Gestion des Kits qui permet de générer un rapport sur les Composants Manquants. Elle compare le contenu réel d’une Liste de Composition du Kit (LCK) avec la Composition Théorique du Kit (TCK) — la composition standard attendue pour ce type de kit.

Le rapport est exporté sous forme de fichier Excel (.xlsx) et est conçu pour aider les équipes d’approvisionnement et d’entrepôt à :

  • Évaluer rapidement le statut de complétude des kits détenus en stock.
  • Identifier les articles manquants ou en quantités inférieures à celles attendues.
  • Soutenir la planification du réapprovisionnement et les évaluations des besoins.
  • Suivre la qualité des kits à l’aide d’indicateurs d’écart (KPIs).

Compréhension des deux documents comparés :

 

LCK — Liste de Composition du Kit

TCK — Composition Théorique du Kit

Définition

Le contenu réel d’un kit physique actuellement en stock

La composition standard / attendue pour ce type de kit (le modèle)

Objectif

Enregistre ce qui se trouve dans le kit

Définit ce qui devrait se trouver dans le kit

Statut pour la comparaison

Doit être Terminé ou Clôturé

Référencé via la version TCL liée dans la LCK

ASTUCE : Les LCK Clôturées comprennent des kits ou modules faisant partie d’un kit parent — ceux-ci sont éligibles à la comparaison.

REMARQUE : La correspondance entre les lignes LCK et TCK utilise une approche dégressive : d’abord par Produit + Quantité + N° Lot/Date d’expiration, puis Produit + N° Lot/Date d’expiration, puis Produit uniquement. Cela garantit la comparaison la plus précise possible.

2. Étape par Étape : Générer le Rapport

Suivez les étapes ci-dessous pour générer le Rapport de Comparaison LCK vs TCK.

1

Ouvrir le module Approvisionnement

Connectez-vous à UniField et cliquez sur Approvisionnement dans le menu de navigation principal.

2

Accéder à la Gestion des Kits

Sélectionnez Gestion des Kits dans la barre de navigation de gauche ou supérieure.

3

Ouvrir les Listes de Composition des Kits

Cliquez sur Listes de Composition des Kits (LCK) pour afficher la liste de toutes les LCK.

4

Filtrer et localiser votre LCK

Utilisez les options de recherche et de filtre pour trouver la LCK que vous souhaitez analyser. Recherchez les LCK ayant le statut Terminé ou Clôturé.

AVERTISSEMENT : Les LCK en brouillon ou en cours ne peuvent pas être utilisées pour la comparaison. Si votre LCK est encore en cours, terminez-la ou clôturez-la d’abord.

5

Ouvrir la LCK

Cliquez sur la ligne LCK pour ouvrir l’enregistrement et consulter ses détails.

6

Confirmer que la version TCK est liée

Dans l’en-tête de la LCK, vérifiez qu’une version TCK (TCL) est référencée. Il s’agit du standard par rapport auquel votre rapport sera comparé.

L’écran ci-dessous montre un enregistrement LCK typique au statut Terminé, prêt pour la comparaison :

Figure : Liste de Composition du Kit — statut Terminé, affichant le produit, la version, la référence et les articles de composition

7

Ouvrir le menu d’actions latéral

Avec la LCK ouverte, localisez le panneau Actions ou le menu latéral droit.

8

Cliquer sur “Rapport de Comparaison TCK LCK”

Sélectionnez cette option dans la section Rapports du panneau latéral droit. Elle n’est visible que pour les LCK au statut Terminé ou Clôturé.

Le lien vers le Rapport de Comparaison TCK LCK se trouve dans la section Rapports du panneau latéral droit (mis en évidence ci-dessous) :

Figure : Panneau Rapports latéral droit — bouton Rapport de Comparaison TCK LCK (mis en évidence)

9

Enregistrer ou ouvrir le rapport Excel

UniField générera automatiquement le rapport et vous invitera à télécharger ou ouvrir le fichier .xlsx.

ASTUCE : Le rapport est généré au format Excel (.xlsx) afin que les équipes d’approvisionnement puissent l’utiliser pour le filtrage, une analyse plus approfondie ou le partage avec d’autres parties prenantes.

3. Mise en Page et Contenu du Rapport

Le rapport Excel généré utilise la mise en page suivante : les colonnes TCK apparaissent en premier (colonnes A–F), suivies des colonnes LCK (colonnes G–M, surlignées en vert clair). Cet ordre reflète la logique opérationnelle utilisée par les équipes d’entrepôt — en partant de ce qui est attendu dans un kit, puis en comparant avec ce qui est réellement présent.

En-tête du Rapport

La partie supérieure du rapport affiche des informations récapitulatives sur le kit :

  • Référence du Kit (Produit)
  • Date de Création du Kit
  • Version TCK (TCL)
  • Numéro de Lot et Date d’Expiration
  • Date de Génération du Rapport

La capture d’écran ci-dessous montre un exemple de rapport généré pour le kit KMEDMEBO05A (module d’échantillonnage Ebola FHV), incluant les détails TCK et LCK ainsi que la section Résumé de Comparaison :

Figure : Rapport de Comparaison TCK LCK — en-tête, détails TCK & LCK, Résumé de Comparaison et lignes produits (KMEDMEBO05A, lot 182394/1/28)

Colonnes du Rapport

Chaque ligne du rapport représente une ligne produit. Les colonnes sont réparties entre les données TCK (attendues) et LCK (réelles) :

Colonne

Section

Description

Code Produit

TCK

Référence produit issue de la Composition Théorique du Kit

Quantité TCK

TCK

Quantité attendue selon la norme TCK

N° Lot TCK / Date d’expiration

TCK

Numéro de lot et date d’expiration issus du TCK

Commentaire TCK

TCK

Tout commentaire saisi sur la ligne TCK

Module LCK

LCK

Le module au sein de la LCK — positionné entre le Commentaire TCK et la Qté Totale LCK

Quantité Totale LCK

LCK

Quantité totale réelle du produit trouvé dans le kit

N° Lot LCK / Date d’expiration

LCK

Lot/expiration réels des produits dans le kit

Écart

Résumé

Différence entre la quantité LCK et TCK (+/−)

REMARQUE : La colonne Emplacement de Stock LCK n’est pas incluse dans le rapport. L’accent est mis sur les références et quantités de produits, et non sur les emplacements de stockage physiques.

4. Résumé de Comparaison et KPIs

Le rapport inclut une section Résumé de Comparaison avec deux indicateurs de performance clés (KPIs) qui offrent une vue d’ensemble du statut de complétude du kit. Ces KPIs suivent la même logique que les rapports d’écart BC vs Catalogue déjà familiers aux utilisateurs d’UniField.

KPI

Formule

Ce que cela indique

Écart d’articles LCK–TCK (%)

((# codes dans LCK − # codes dans TCK) / # codes dans TCK) × 100

Positif = plus de types de produits dans la LCK qu’attendu. Négatif = des types de produits manquent dans la LCK.

Écart de Quantité LCK–TCK (%) par produit

((Qté dans LCK − Qté dans TCK) / Qté dans TCK) × 100

Affiché par produit. 0% est exclu. Les valeurs négatives apparaissent en rouge dans le résumé du rapport.

Écart de Quantité — Exemples pratiques :

Scénario

Qté LCK

Calcul

Écart

Kit complet

100 (correspond au TCK de 100)

(100 − 100) / 100 × 100

0% — exclu du résumé

Léger manque

95 (TCK requiert 100)

(95 − 100) / 100 × 100

−5% (mis en évidence en rouge)

Surplus

110 (TCK requiert 100)

(110 − 100) / 100 × 100

+10%

Manque important

60 (TCK requiert 100)

(60 − 100) / 100 × 100

−40% (mis en évidence en rouge)

REMARQUE : Les valeurs d’écart négatives sont surlignées en rouge dans le Résumé de Comparaison. Les écarts de 0% sont exclus du champ Écart de Quantité pour garder le résumé lisible.

ASTUCE : Si tous les articles correspondent exactement au TCK, le résumé affichera un écart de 0% ou un message confirmant que le kit est complet sans articles manquants.

F. HOW TO IMPORT AN EXCEL DELIVERY ORDER FILE


Supply User Manual ENG -> 5. Warehouse -> 5.6 LU-SU4105: Delivery Orders -> F. HOW TO IMPORT AN EXCEL DELIVERY ORDER FILE

F. HOW TO IMPORT AN EXCEL DELIVERY ORDER FILE

Delivery Document (OUT)  can be imported from an Excel file.

Go to: Warehouse / Warehouse Management / Deliveries / Delivery orders

  1. Select Delivery Order you want to import
  2. Click “Process” on the OUT that you wish to import
  3. Click on “Import OUT”.

Note that there is a check on qty that must be lower or equal to Ordered Qty

The data is imported to the main screen and manual validation is still needed to process the document forward.

E. HOW TO EXPORT AN EXCEL DELIVERY ORDER FILE

Supply User Manual ENG -> 5. Warehouse -> 5.6 LU-SU4105: Delivery Orders -> E. HOW TO EXPORT AN EXCEL DELIVERY ORDER FILE

E. HOW TO EXPORT AN EXCEL DELIVERY ORDER FILE

Delivery Document (OUT)  can be exported to an Excel file.

Go to: Warehouse / Warehouse Management / Deliveries / Delivery orders

  1. Select Delivery Order you want to export
  2. Click on the button “Export OUT” on the form view of your Delivery Order

     3. An Excel version of the OUT is open. You may save or update it as needed.

D. Report – Product Status Inconsistencies

Supply User Manual ENG -> Products -> 3.7 Products Reports -> D.Report – Product Status Inconsistencies

D. Report – Product Status Inconsistencies

This report is generated in excel at Coordination level and shows every product which has the Status discrepancy between Coordination and Projects, the header information of the product is displayed (code, description, product creator, Standardization Level, UniData status). OC guidelines should be consulted before taking any further action.

Go to: Products>Reporting> Product Status Inconsistencies

E. How to export an Internal Request.

Supply User Manual ENG -> 4. Procurement -> 4.2 LU-SU3101: Internal Requests (IRs) -> E. How to export an Internal Request.

E. How to export an Internal Request.

As for the import, the system offers several options to export the lines from an Internal Request to an Excel file. Depending on whether you need to export only product lines or product lines AND header information you will need to choose the correct link in the right action menu.

Go to: Order / Order / Internal Requests

  1. Click on the check box on the left side of the line corresponding to the Internal Request to be exported.
  2. The Action menu on the right-hand side is displayed.
  3. Click on the

3.1 “Internal Request Excel Export” link to export product lines only

3.2 “Export to IR Excel template” link to export product lines AND header information

3.3 “Export Product List IR Excel” can be accessed in the IR List view Action menu (without any IR being selected). In the intermediate pop-up, the user can select an existing Product list. 

4. The IR will be exported to Excel.

3.1 Exporting an IR to Excel

All the information of the IR you chose will be exported to Excel with the following format:

3.1 IR Excel export
3.2 Exporting to IR Excel template
3.2 Export to IR Excel template

Do not mix-up these 2 export options with the “Export” option available at the bottom of the action menu which will export all the headers of the IRs appearing on the screen (without the details of the product lines).

3.3 Export Product List IR Excel template ( select Product list to export)
3.3 “Export Product List IR Excel”

From the same screen, you can produce (and print) a PDF report for validation purpose using the option “Internal Request” also located in the action menu (under “Reports“). Note that these exports can also be done from within the IR.

Exporting an IR to PDF from the “Search: Internal Requests” screen
Exporting an IR to PDF from within the IR
Internal Request in PDF format

Note 1: It is possible to select several IRs at the same time on the “Search: Internal Requests” screen (using several check boxes) and export them in one click to Excel or PDF. In Excel, you will get one IR per sheet. In PDF, all the selected IRs will be exported on one PDF file.

Note 2: The export to Excel and PDF can also be done from within the IR as the “Internal Request Excel Export“, “Export IR Excel template” and the “Internal Request” options are also available in the action menu (under “Reports“).

Note 3: On the Excel, the comment included in the “Comment instead of the product” column of the IR will appear in the column “Comment“. Note that the notes included in the “Notes” column of the IR are not exported to excel.

Note 4: On the PDF, at header level, the notes inserted on the “Notes” tab of the IR will appear (at the bottom of the PDF, behind “REMARKS“). At line level, the notes included on each line of the IR will appear (in the column “Notes” of the PDF) but the “comment instead of the product” information won’t appear except for lines with “product by nomenclature“.

Note 5: On the PDF, “Cancelled” lines will not be displayed

B. How to create a supplier product catalogue price list

Supply User Manual ENG -> Products -> 3.4 LU-SU2103: Products in Supplier Catalogues -> B. How to create a supplier product catalogue price list

B. How to create a supplier product catalogue price list

In order to create a Supplier Catalogue Price List for a supplier, the user should follow the relevant MSF procedures outlined for gathering this sort of information, commonly known as market analysis (which may involve a Tendering process) before entering this data into the system. To make this inputting process as efficient as possible, it is possible to both enter this information directly into the Supplier/Product record as well as to import the data into the system via an excel file.

To enter the Supplier Catalogue Price List directly into the system, Go to: Partners/Suppliers

  1. Enter the relevant search values in the header fields to find the Supplier you want
  2. Tick the checkbox next to the supplier in the list view
  3. In the Actions Menu on the right-hand side, click on New Catalogue. A screen displaying New

Catalogue will appear.

Product catalogue – 1

  1. Enter the Name (how you want to call this Supplier’s catalogue)
  2. The “From” field will automatically display today’s date but can be edited
  3. Enter the “To” date using the calendar button. This should reflect the last day on which the information you are entering is valid (e.g. if the price is fixed how long it is fixed at this price according to the supplier’s bid). This field is not mandatory.
  4. The currency will pull through from the currency entered for this supplier
  5. Each new catalogue must have a ranking. A default “3rd choice” ranking is automatically assigned for catalogues created via synch or auto VI import but can be changed.
  6. The Partner field will display the name of the Supplier that for which you are adding the catalogue price.
  7. The Active box will reflect the state from the Supplier record (i.e. this should have been ticked if we are considering using them and have asked for product pricing etc)
  8. In the Import Line section, the Add Attachment button will allow us to browse and select the excel file that we want to import, and next to this is the “Import file” button which will import the data from the excel file.
  9. To Add products individually to the catalogue, in the Products tab, click on the New button
  10. Click on the magnifying glass icon earchto bring up the search products window and enter the relevant values to find the product(s).
  11. Select all relevant products, and check that the default UoM is correct (or changing it if need be)
  12. Enter the minimum quantity which the supplier had based their price on. If there is none then 1 can be entered. If you try to save a line with 0 as a minimum quantity, the system will display an error message
  13. Enter the Unit Price (which should be related to currency selected)
  14. Enter any SoQ Rounding figure (e.g. if Pens are the product, the UoM and price may be per pen (i.e. pce), but the supplier sells the pens in packets of 50, in which can the rounding would be 50.)
  15. Enter the minimum order quantity – depending on the supplier, the lowest quantity of the goods they would accept to supply per order
  16. Enter any other comment
  17. Click on the floppy disk icon ave record to save the line and either repeat the steps to add another product or click on the Save button to save the catalogue list.
  18. When catalogue is complete and all lines are saved, user can confirm catalogue by clicking on the Confirm button. This means all data it contains will be used by system for relevant transactions.

Product catalogues – 2

N.B: It is possible to have 2 active catalogues for the same supplier in the same instance as long as the products are different in each catalogue. If one supplier has more than one catalogue for the same product, user will receive a warning message.

Please note that it is possible to create a Catalogue of the Coordination instance at coordination instance. This function has been added to enable the related projects, to which this catalogue is synchronized down, to have a Coordination Supplier Catalogue. This will help to get more accurate estimation prices for intra-mission orders.