Search
Related topics are listed below.
Data types and arrays
AFD 2.0 building blocks » Data types and arrays
Data types In AFD 2.0, data types and format restrictions are separated. As a result, AFD 2.0 only has seven native data types: integer, decimal, string, date, time, timestamp and boolean. The inclusion of boolean instead of ADNLOG implements a much-anticipated wish…
policy
AFD 2.0 building blocks » Entities » Core entities » policy
Entity: policy The policy entity acts as a container for the grouping of policy-related data. A policy is a legal document issued to the insured setting out the terms of the contract of insurance. Example usage Below is an example policy entity of entityType…
Unique identifiers and referrals
AFD 2.0 building blocks » Unique identifiers and referrals
Defining entities uniquely within the context of a message It must be possible for every instance of an entity to be uniquely identified within an AFD message, structure or function. This can be done in two ways: with functional and/or technical identifiers. With…
Error messages SOAP and REST
Transaction standards » Error messages SOAP and REST
The information in this chapter is described with the REST architecture principles in mind. One of the key elements of that architecture is the fact that data exchange is based directly on the HTTP protocol, and does not use an intermediate layer for functions or…
Alignment existing SIVI documentation and AFS
Manual SIVI All Finance Standard » Alignment existing SIVI documentation and AFS
A lot of SIVI documentation, related to SIVI AFS, is available on the SIVI website. Most of this information is written in Dutch. The goal of SIVI is to add an English translation of this documentation to the SIVI AFS Manual. You can find some useful links to SIVI…
Operation and variant description: reading guide
Domain specific functions » Introduction to all functions » Operation and variant description: reading guide
This chapter is a reading guide to the detailed descriptions of all variants applicable for a cluster/operation combination. A general overview of the API-framework is available in Overview of the API-framework. You can find a detailed overview of all functions in…
Differences between AFD 1.0 and AFD 2.0
Manual SIVI All Finance Standard » Differences between AFD 1.0 and AFD 2.0
All Finance Data Catalog English as official language The demand for English documented SIVI standards is increasing. The first reason is that software development activities at for instance insurers, service providers and suppliers are increasingly (at least partly)…
financialTransaction
AFD 2.0 building blocks » Entities » Supporting entities » financialTransaction
Entity: financialTransaction The financialTransaction entity is used for grouping transaction related data, such as bookings, benefits and deposits. Example usage Below is an example financialTransaction entity of entityType booking, filled with some attributes.…
premium
AFD 2.0 building blocks » Entities » Supporting entities » premium
Entity: premium The premium entity is used for grouping premium-related data. A premium is the amount of money an individual or business must pay for a policy. The premium entity is typically used in conjunction with a policy entity. Example usage Below is an…
masterAgreement
AFD 2.0 building blocks » Entities » Supporting entities » masterAgreement
Entity: masterAgreement The masterAgreement entity is used for grouping data about a master agreement, such as a package policy, framework contract or group discount arrangement. The masterAgreement entity is used in combination with loan, pension and/or policy…
Standard attributes
AFD 2.0 building blocks » Attributes » Standard attributes
If attributes are sufficiently generic across the entire financial industry, they are suitable for standardization, and thus for inclusion in AFD. These attributes are standard attributes. Entities can be filled from a list of associated attributes. For example, the…
AFD 2.0 building blocks
AFD 2.0 building blocks
Outline of this chapter This chapter describes the building blocks of AFD 2.0. The All Finance Data catalog consists of entities, attributes, data types, codelists and code values: An entity describes an object or thing from reality, for example a policy, party or…
coverage
AFD 2.0 building blocks » Entities » Core entities » coverage
Entity: coverage The coverage entity is intended for the grouping of coverage-related data. A coverage is the protection provided by the policy against a certain risk. Example usage Below is an example coverage entity of entityType hullVehicle, filled with some…
condition
AFD 2.0 building blocks » Entities » Supporting entities » condition
Entity: condition The condition entity is used for grouping condition-related data, for example policy conditions. The condition entity can also be used for employment-related conditions. Example usage Below is an example condition entity, filled with some…
clause
AFD 2.0 building blocks » Entities » Supporting entities » clause
Entity: clause The clause entity is used for grouping information about a clause which is included in a contract (such as a policy). Example usage Below is an example clause entity, filled with some attributes. See AFD 2.0 Online for the complete and up-to-date data…
masterAgreementStructure
AFD structures » masterAgreementStructure
General properties The masterAgreementStructure can be used to define a collection of contracts which are linked to each other by a master agreement, for example a package policy, or a framework pension contract. A masterAgreementStructure always consists of a single…
Entities
AFD 2.0 building blocks » Entities
An entity describes an object or thing from reality, for example a policy, party or claim. AFD 2.0 consists of about thirty entities, which can be roughly divided into three categories: core entities (claim, coverage, loan, object, party, pension, policy), supporting…
claim
AFD 2.0 building blocks » Entities » Core entities » claim
Entity: claim The claim entity is used for the grouping of claim-related data. A claim is a request made by the insured for insurer remittance of payment due to loss incurred, and covered under the policy agreement. Example usage Below is an example claim entity,…
commonFunctional
AFD 2.0 building blocks » Entities » Technical entities » commonFunctional
Entity: commonFunctional The commonFunctional entity covers all information about the content of the message. This is typically domain-specific information, while the commonTechnical entity primarily provides technical message-related meta-data. Example usage Below…
afsElement
AFD 2.0 building blocks » Entities » Supporting entities » afsElement
Entity: afsElement Details about an afsElement, for instance a customAttribute. Custom attributes are new in AFD 2.0. They allow parties to temporarily define attributes that do not belong in the AFD 2.0 model: attributes that are not generic enough for the entire…
Task
Domain specific functions » Task
Clusters are grouped functions with the same characteristics and use. The cluster task contains general information about an assignment or task, for example, inspection, valuation or repair of damage. An overview of the clusters can be found in the Overview of the…
Insuring multiple objects
AFD structures » Insuring multiple objects
SIVI designed agreements and principles for the insurance of multiple objects as part of one policy. Within this scope, we specify three different policy constructions: Single policy: a separate or single policy per object, each with its own coverage, clauses and/or…
Proprietary APIs
Proprietary APIs
The objective of the SIVI AFS API-framework is to provide a blueprint for generic functions that are used in the value chain of financial products. This enables parties to model their APIs in a standard format which is recognizable throughout the industry and…
policyStructure
AFD structures » policyStructure
General properties The main characteristics of the policyStructure are the presence of the policy entity, a party entity with entityType policyHolder, an object entity to record the insured object, and a coverage entity to describe the protection provided by the…
AFD structures
AFD structures
Outline of this chapter In the next sections the different structures are explained and defined. For each structure, it is indicated which entities can be used within the structure, and their occurrence requirements. Depending on the actual use of the structure,…
Termination
Domain specific functions » Contract » Termination
The operation termination of a contract puts an end to a policy, loan, pension, master agreement or contract within a master agreement. *The functions, variants and structures concerning pension and loan are under construction and will follow in due time. How to use…
Introduction to AFD structures
AFD structures » Introduction to AFD structures
Bridge between data catalog and API-framework functions In SIVI AFS, the use of AFD structures occupies a prominent place. In thinking about API architectures, the starting point is that functions are defined on the basis of the specific data set to which the function…
Change
Domain specific functions » Contract » Change
The operation change of a contract will replace an entity partially or completely. An entity linked to a contract can be a policy, loan, pension, master agreement or contract within an existing master agreement. The payload consists of the structures needed in the…
Special limit
Domain specific functions » Contract » Special limit
The operation specialLimit requests and sends messages and registers contracts with conditions that deviate from the usual (standard) conditions. If contracts would have fit in the usual conditions the operation new would have been applicable. *The functions, variants…
Design principles
Domain specific functions » Introduction to all functions » Design principles
Introduction The All Finance API-framework describes API functionality as much as possible in general terms. Where technical context is relevant or needed the REST design principles are used. REST is a set of architectural constraints, not a protocol or a standard. In…
Renewal
Domain specific functions » Contract » Renewal
The operation renewal will return financial information or calculate the rate as a result of a renewal of a policy, loan, pension, master agreement or contract within a master agreement. *The functions, variants and structures concerning pension and loan are under…
Standard codelists
AFD 2.0 building blocks » Codelists » Standard codelists
Instead of a data type, the format of an AFD attribute can also be based on a codelist. With a codelist, the number of permitted values of an attribute can be limited further than in the case, a generic data type is used. For example, the attribute tripPurpose is of…
Retrieve
Domain specific functions » Contract » Retrieve
The operation retrieve will fetch a policy, loan, pension, master agreement or contract within an existing master agreement for a single entry, a range or a list of entries. The output consists of the structures needed in the particular situation, so it can be a…
New
Domain specific functions » Contract » New
The operation new in case of a contract will add a new policy, loan, pension, master agreement or contract within an existing master agreement). The payload consists of the structures needed in the particular situation, so it can be a policyStructure, a loanStructure,…
Initiate
Technical functions » Session » Initiate
*Under construction More detailed information on Session will follow in due time. Request for a url to initiate a browser session with prefilled data. Access to the API and the URLs provided through the API is subject to adequate security measures for…
Swagger examples of domain specific functions
Domain specific functions » Swagger examples of domain specific functions
The SIVI AFS API framework and the overview of functions are the starting point for opening up APIs to the market. In this section we describe how this framework works, using some examples in SwaggerHub. By clicking the green button below, the user gets access to these…
Security
Security
*Under construction A more up-to-date description of Security will follow in due time. Integral security agreements In daily practice it is very difficult to make integral security agreements throughout the distribution chain for all systems of all chain parties.…
AFD Short
Mapping » AFD Short
Based on the article ‘AFD Short – AFD 2.0-structuur met AFD 1.—attribuutnamen’ (in SIVI AFS Magazine June 2023). Transition to AFD 2.0 The transition from AFD 1.0 to AFD 2.0 was necessary for many reasons. In addition to the switch from…
Custom attributes
AFD 2.0 building blocks » Attributes » Custom attributes
Background Standard attributes do not always cover all situations, required by parties or processes. For example the development of a web service for the acceptance and premium calculation of a car insurance policy. In the data catalog of SIVI AFS you can find the…
Table
Domain specific functions » Table
In order to maintain consistency and traceability in the distribution chain, it is important that parties can exchange data in a tabular structure. The cluster table enables retrieval of information to incorporate in an agent application. It is a way to ensure that…
Claim
Domain specific functions » Claim
Clusters are grouped functions with the same characteristics and use. The cluster claim contains all data needed for claims handling. An overview of the clusters can be found in the Overview of the API-framework. The clusters are concentrated around AFD structures.…
Contract
Domain specific functions » Contract
Clusters are grouped functions with the same characteristics and use. The cluster contract contains everything for the contract administration or policy administration. An overview of the clusters can be found in the Overview of the API-framework. The clusters are…
Introduction All Finance Data Catalog
AFD 2.0 building blocks » Introduction All Finance Data Catalog
Context and history The All Finance Data Catalog (AFD) forms the basis for the digital ecosystem (see also Introduction SIVI AFS). AFD determines how one denotes data (e.g. a date always in the same format) and how one groups this data in a structure (e.g. what data…
XML
Transaction standards » XML
Introduction XML is the abbreviation for Extensible Markup Language. XML is a syntax used in computer programming to enable use of data in a structured way. XML is a platform independent syntax, maintained by W3C. Specific industry standards such as SOAP, XML Schema,…
claimStructure
AFD structures » claimStructure
General properties The claimStructure is made up of entities used to notify and register a loss, process a claim and create settlements. Given the fact that a claim is made against the cover of a policy, the policy and coverage entities are available in the…
underwriting
AFD 2.0 building blocks » Entities » Supporting entities » underwriting
Entity: underwriting The underwriting entity is used for grouping underwriting-related data. Here, underwriting is an inquiry to determine whether or not the risk is acceptable, and to establish all facts that might affect the risk. AFD 2.0 has approximately around…
process
AFD 2.0 building blocks » Entities » Supporting entities » process
Entity: process The process entity is used for grouping process-related data. Within the context of AFD 2.0, processes describe information about a status, associated with (for example) an application or a change. Example usage Below is an example process entity of…
Data registration vs services
Domain specific functions » Data registration vs services
Based on the article ‘SIVI AFS: Registratie van gegevens versus services’ (in SIVI AFS Magazine May 2022). Users of SIVI AFS use AFD 2.0 for the performance of services (data exchange) and for registration (data storage). In this article, we show some…
party
AFD 2.0 building blocks » Entities » Core entities » party
Entity: party The party entity is intended for grouping party-related data. A party may be a (natural) person or an organization. Example usage Below is an example party entity of entityType policyHolder, filled with some attributes. See AFD 2.0 Online for the…
service
AFD 2.0 building blocks » Entities » Supporting entities » service
Entity: service The service entity gives information about agreements (via subscriptions/contracts) regarding the provision of services such as (financial) advice, mediation and (contract) management. Example usage Below is an example service entity, filled with…
note
AFD 2.0 building blocks » Entities » Supporting entities » note
Entity: note If a user wants to enter general information and add his own text, he can use the note entity. Example usage Below is an example note entity, filled with some attributes. See AFD 2.0 Online for the complete and up-to-date data catalog with all available…
New
Domain specific functions » Claim » New
The operation new in case of a claim is used to initiate the claim process with a first notification of loss. The insurance provider creates a claim file and assesses the claim. In the following steps the claim can be rejected, or claim handling will commence. These…
contactDetails
AFD 2.0 building blocks » Entities » Supporting entities » contactDetails
Entity: contactDetails The contactDetails entity is used for grouping contact details such as email addresses or telephone numbers. Example usage Below is an example contactDetails entity, filled with some attributes. See AFD 2.0 Online for the complete and…
task
AFD 2.0 building blocks » Entities » Supporting entities » task
Entity: task The task entity contains general information about a task for, for example, inspection, appraisal or repair of damage. Example usage Below is an example task entity, filled with some attributes. See AFD 2.0 Online for the complete and up-to-date data…
object
AFD 2.0 building blocks » Entities » Core entities » object
Entity: object The object entity is intended for the grouping of object-related data. Within the context of AFD, an object is in general an insured or financed object. Example usage Below is an example object entity of entityType motorVehicle, filled with some…
partyStructure
AFD structures » partyStructure
General properties In many customer folders, the party is located in the center of a web of contracts around it, varying from pensions to policies and even telephone companies or energy contracts, often with explicit relationships to other parties in the database. A…
document
AFD 2.0 building blocks » Entities » Supporting entities » document
Entity: document The document entity is used for grouping information about an attachment or document. Example usage Below is an example document entity, filled with some attributes. See AFD 2.0 Online for the complete and up-to-date data catalog with all available…
loan
AFD 2.0 building blocks » Entities » Core entities » loan
Entity: loan The loan entity acts as a container for the grouping of loan-related data. A loan is a form of contract between a borrower and a lender which regulates the mutual promises made by each party, usually about a sum of money, for example as a mortgage for…
financialInformation
AFD 2.0 building blocks » Entities » Supporting entities » financialInformation
Entity: financialInformation The financialInformation entity is used for grouping financial related data not pertaining to a transaction. The financialInformation entity can be used for anything from expenses data to invoices and VAT/GST information. Example…
error
AFD 2.0 building blocks » Entities » Technical entities » error
Entity: error The error entity is intended for communicating error messages, primarily used within the API-framework. Example usage Below is an example error entity, filled with some attributes. This example shows a check of the POR code at the moment of receival…
investment
AFD 2.0 building blocks » Entities » Supporting entities » investment
Entity: investment The investment entity contains financial information and can be used to explicitly model financial information about investments within a separate entity. Example usage Below is an example investment entity, entityType investmentDetails, filled…
profileQuestions
AFD 2.0 building blocks » Entities » Supporting entities » profileQuestions
Entity: profileQuestions The profileQuestions entity is used for grouping questions asked to set up a customer profile, for example in a mortgage application process. A customer profile consists of the knowledge and experience of the customer, his objectives and his…
pension
AFD 2.0 building blocks » Entities » Core entities » pension
Entity: pension The pension entity acts as a container for the grouping of pension-related data. A pension is a contract from which periodic payments are drawn to support (for example) a person’s retirement from work. Example usage Below is an example pension…
discountOrSurcharge
AFD 2.0 building blocks » Entities » Supporting entities » discountOrSurcharge
Entity: discountOrSurcharge The discountOrSurcharge entity is used for grouping data about a discount or surcharge. A discount is a percentage or amount deducted from (for example) a premium to be paid by the insured, a surcharge is an additional sum to be paid.…
poolShare
AFD 2.0 building blocks » Entities » Supporting entities » poolShare
Entity: poolShare The poolShare entity is used for grouping pool share-related data. A pool share is, within the context of AFD 2.0, the relative size of the participation by an insurer in a contract. Example usage Below is an example poolShare entity, filled with…
address
AFD 2.0 building blocks » Entities » Supporting entities » address
Entity: address The address entity is used for grouping address-related data. The definition of an address is broad. On the one hand an address is an indication of a location that a person can visit or that has been recognized by a postal service. On the other hand…
settlement
AFD 2.0 building blocks » Entities » Supporting entities » settlement
Entity: settlement The settlement entity is used for grouping information regarding the handling of a claim. The entity can be used for supporting a claim. Example usage Below is an example settlement entity, filled with some attributes. claimRef refers to the…
ticket
AFD 2.0 building blocks » Entities » Supporting entities » ticket
Entity: ticket The ticket entity contains general information about a question, complaint or claim file. A common example is creating a ticket when registering an incident for the first time. Example usage Below is an example ticket entity, filled with some…
commonTechnical
AFD 2.0 building blocks » Entities » Technical entities » commonTechnical
Entity: commonTechnical The commonTechnical entity covers all information about sending or storing the message. This is typically technical information, while the commonFunctional entity primarily provides domain-specific message-related meta-data. Example…
incident
AFD 2.0 building blocks » Entities » Supporting entities » incident
Entity: incident The incident entity is used for grouping information about the circumstances and damage/loss due to an incident. The entity can be used for supporting a claim. Example usage Below is an example incident entity, filled with some attributes. claimRef…
partyDetails
AFD 2.0 building blocks » Entities » Supporting entities » partyDetails
Entity: partyDetails The partyDetails entity is used for grouping specific information about a given party, such as health or income data. The entity can be used for supporting a party entity (for example of entityType policyHolder or regularDriver). Example…
Mortgage domain mapping
Mapping » Mortgage domain mapping
Based on the article ‘SIVI AFS nu ook geschikt voor modellering hypotheekdomein’ (in SIVI AFS Magazine December 2022). Introduction With the SIVI All Finance Standard (SIVI AFS), it is possible to model the first facets of the mortgage domain. This is the…
JMESPath
AFD-definition standard » JMESPath
JMESPath is used for defining specifications of validation rules between attributes that cannot be specified in JSON Schema. The use of JMESPath definitions promotes the creation of unambiguous specifications. JMESPath can be used to check the dependency between two or…
Mapping-API
Mapping » Mapping-API
Based on the article ‘Mapping van AFD 1.0 naar AFD 2.0 geautomatiseerd’ (in SIVI AFS Magazine May 2022). Mapping-API for all mappings related to SIVI AFS SIVI offers an API to provide mappings from one data catalog to another. More specific, the API…
action
AFD 2.0 building blocks » Entities » Supporting entities » action
Entity: action An action is a task that a party must perform in response to one or more events. An action is often used in combination with a signal entity. Example usage The example below shows some actions related to the life event turning 18 (‘18 jaar…
JSON
Transaction standards » JSON
Introduction JSON is the abbreviation for JavaScript Object Notation. JSON is a syntax used in computer programming for using data in a structured way. JSON is a platform independent, open-standard syntax. Specific open standards such as JSON Schema and AJAX have been…
Attributes
AFD 2.0 building blocks » Attributes
An attribute describes a characteristic of an entity, for example the date of birth (attribute) of the policyholder (entity), the expiry date (attribute) of the policy (entity), etc. A single entity may contain multiple attributes. Attributes are grouped by entity in…
afsTable
AFD 2.0 building blocks » Entities » Supporting entities » afsTable
Entity: afsTable The afsTable entity is used for grouping data as a table, which can either be a (customized) codelist or a freely definable table using the tableColumn and tableRow entityTypes. See the example below for such a self-defined table: the table is given a…
Object
Domain specific functions » Object
Clusters are grouped functions with the same characteristics and use. The cluster object contains all data with respect to an insured or financed object representing an interest for the owner. An overview of the clusters can be found in the Overview of the…
Party
Domain specific functions » Party
Clusters are grouped functions with the same characteristics and use. The cluster party contains all data with respect to a natural person or an organization. An overview of the clusters can be found in the Overview of the API-framework. The clusters are concentrated…
signal
AFD 2.0 building blocks » Entities » Supporting entities » signal
Entity: signal A signal is a message from a party (usually an intermediary or insurer) to a natural person (usually the consumer) following an event (eg. the customer has turned 18) with the request to take action (eg. updating of payment details). There are two kinds…
Codelists
AFD 2.0 building blocks » Codelists
A codelist can limit the number of permitted values of an attribute. In data modelling terms, a codelist can be seen as an enum(eration) of values allowed. An example codelist of the attribute ‘primaryColors’ could be the enumeration [‘yellow’, ‘blue’,…
Readers guide
Manual SIVI All Finance Standard » Readers guide
This manual describes and explains the SIVI All Finance Standard (SIVI AFS). If you have a managerial role, reading this chapter and subsequently paragraphs 2.1, 5.1 and chapter 14 will give you an overall impression of SIVI AFS. For those with a more substantive…
VNAB-SIVI AFS mapping
Mapping » VNAB-SIVI AFS mapping
Based on the article ‘Opstellen eerste VNAB-berichten mogelijk binnen SIVI AFS’ (in SIVI AFS Magazine December 2022). The iDOSpl@tform of the VNAB (Dutch Insurance Exchange Association) facilitates a user-friendly and structured exchange of data such as…
taskStructure
AFD structures » taskStructure
General properties The main characteristics of the taskStructure are the presence of the task entity, which groups general information about a task for, for example, inspection, appraisal or repair of damage. Therefore, claim and claim-related entities (party, policy)…
ticketStructure
AFD structures » ticketStructure
General properties Within the insurance market, it is quite common to process customer reports using ‘tickets’. A ticket entity, including a ticketStructure and according attributes is available to support these processes. Mandatory components The table…
JSON Schema
AFD-definition standard » JSON Schema
Context JSON Schema is used for defining specifications of messages regarding structures, entities and attributes. The use of JSON Schema promotes the preparation of unambiguous specifications. In addition, JSON Schema can be used as a basis for automated checking of…
Change
Domain specific functions » Claim » Change
The operation change in case of a claim will replace an entity partially or completely, if the processes for handling and settling claims have not been completed, yet. A change to a claim might be necessary, for example, if the claim needs to be linked to another…
AFD-definition standard
AFD-definition standard
*Under construction. The AFD-definition Standard manual can be consulted in Dutch. The English version of the AFD-definition Standard 2.0 will be available soon. Introduction The digitization of insurance processes continues unabated. Applications and data exchange…
Additional support
Additional support
Manual This manual is the first place of information for users of the AFD, API-framework and AFD-definitions. If information is missing or something is unclear, please contact support@sivi.org or call within office hours (030) 698 80 90. Requests for changes and…
Message exchange platform
SIVI protocols » Message exchange platform
*Under construction A more thorough description of the Message exchange platform will follow in due time. Introduction The basic goal of a message exchange platform is the secure interchange of structured and unstructured data, as well as documents among trusted…
Retrieve
Domain specific functions » Table » Retrieve
The operation retrieve will fetch data in a tabular structure for use in automated processes and user dialogs. Automated processes often use codelists to enforce the use of valid values for a specific attribute and keep the dataset compact. In a screen dialog this is…
SOAP vs REST
Transaction standards » SOAP vs REST
*Under construction A more up-to-date description of the Transaction standards will follow in due time. Introduction The choice of a specific technical solution or application remains the responsibility of the individual party who develops an API, which is why the…
superStructure
AFD structures » superStructure
*The description of the superStructure is under construction: more examples and elaborations will follow in due time. Structures: general rules The general rule for structures is that structures should not be nested under other structures: for example, if you want to…
Overview of all functions
Domain specific functions » Overview of all functions
Introduction The SIVI API-framework function overview contains two documents. One document is based on the Category Functional and contains all the functional functions of this framework. The other document is based on the Category Technical and contains all the…
Manual SIVI All Finance Standard
Manual SIVI All Finance Standard
This manual describes and explains the SIVI All Finance Standard (SIVI AFS). If you have any questions about this manual or suggestions for improvement, please do not hesitate to contact support@sivi.org or call within office hours (030) 698 80 90. Version…
Retrieve
Domain specific functions » Object » Retrieve
The operation retrieve in case of an object will fetch the data of an object. Different entity types are available within the objectStructure, for example motorVehicle or building. You can find a complete overview in AFD 2.0 online. How to use variants The…
Introduction SIVI AFS
Manual SIVI All Finance Standard » Introduction SIVI AFS
SIVI digital ecosystem Within the financial services distribution, data and IT are increasingly preconditions for both the shaping of business activities (like acceptance of an insurance policy) and the development of customer services (for instance an insurance…
New
Domain specific functions » Task » New
The operation new in case of a task will create a new task for a third party. Examples of tasks are inspection, valuation or repair of damage. The entityType assignment is always used in case of operation new. How to use variants This function is used to outsource a…
Overview of the API-framework
Domain specific functions » Introduction to all functions » Overview of the API-framework
The API-framework is designed in four levels to find the right API in a few steps. The four levels of the API-framework are: Category Cluster Operation Variant In the remainder of this section all elements will be explained. Figure 5.1.1-1 API-framework…