Customer Release Notesdownload.safran.no/Download/Doc/Project/ver731/CRN... · Safran Project 7.3.1 needs an upgraded database. The Safran Project database needs to be version 7.3.1.

Customer Release Notes

for

Safran Project version 7.3.1 Build: 119091

(Last update: Oct 5th, 2019)

Customer Release Note Safran Project 7.3.1

1

Copyright © 1997-2019 Safran Software Solutions AS. All rights reserved. Notice Safran is a registered trademark; Safran Project, Safran Planner, Safran Risk, Safran for Microsoft Project, Safran for the Microsoft Project Platform, Safran Web Access, Safran Integrator for SAP, Safran Enterprise Developer, Safran Details and Safran Details Developer are trademarks of Safran Software Solutions AS. All other brands or names are trademarks or registered trademarks owned by their respective holders.


2

Introduction

These Customer Release Notes, or CRN for short, contain information about Safran Project 7.3.1.119091. We highly recommend reading this document carefully before installing this release of Safran Project. This release of Safran Project is considered a version upgrade; it includes new features and some fixes from previous builds. This release note was last updated on October 5th, 2019.

Accuracy This document is for information purposes only, and the content is subject to change without notice and does not represent a commitment on the part of Safran Software Solutions AS. Every effort has been made to ensure the accuracy of the features described in this publication; however, Safran Software Solutions AS offers no guarantee either expressed or implied for the accuracy of this publication and the described features herein or the applicability of described techniques. Safran Software Solution AS may alter the features described without notice.

About this document If you are upgrading from Safran Project 7.3.0, we recommend reading “Summary of changes from Safran Project 7.3.0”. If you are upgrading from Safran Project 7.2, we recommend that you also read “Summary of changes from Safran Project 7.2”. All of you should also read the chapter “Before you install,” before starting the installation.


3

Before you install

▪ Backup/archive all data before updating the software. (The default location of the local database (if you have a previous installation of Safran Project Personal) is %appdata%/safran. It may, however, reside elsewhere.

▪ Read these Customer Release Notes carefully.

▪ Read the “Install Guide for Safran Project 7.3.1” carefully.

▪ Safran Project 7.3.1 needs an upgraded database. The Safran Project database needs to be version 7.3.1. The Personal Edition contains an updated local database ready to use.

▪ If you are upgrading from Safran Project v5, Safran Project v7.0, Safran Project 7.1 or 7.2, you should uninstall the previous version before you install Safran Project 7.3.1


4

Table of Contents

Important information about supported versions of Safran Project ....................................... 5

Important information before upgrading to Safran Project 7.3.1 for users of Safran Risk ....... 5

Summary of Changes from 7.3.0............................................................................................ 6

Summary of Changes from 7.2 .............................................................................................. 8

Issues fixed with 7.3.1 Build 119091 .................................................................................... 11

Issues fixed with 7.3.0 Build 119041 .................................................................................... 14

Changes to database definitions upgrading from v7.3.0 ...................................................... 17

Changes to database definitions upgrading from v7.2 ......................................................... 24

Documentation ............................................................................................................... 26

Supported Environments ................................................................................................. 26

Technical Support ............................................................................................................ 27


5

Important information about supported versions of Safran Project With this release of Safran Project, the supported versions are Safran Project 7.3 and Safran Project 7.2. Support for Safran Project 7.2 ends twelve months after releasing Safran Project 7.3. Support for 7.2 will, therefore, end December 1st, 2019.

Important information before upgrading to Safran Project 7.3.1 for users of Safran Risk If you are running Safran Risk on the same machine as Safran Project you should delay the upgrade to Safran Project 7.3.1 until you can also upgrade Safran Risk to version 7.3.1.


6

Summary of Changes from 7.3.0 Performance improvement The significant change from version 7.3.0 is related to saving large amounts of data to the database. We rewrote the save function. When there is a large amount of data to be saved to the database, it uses bulk save technology. Instead of saving line by line to the database, it saves bulks of data to the database. The bulk save functionality has been implemented on project import when using the overwrite function. Bulk save is used when saving baseline data (when setting a new Baseline), when saving progress data (when running a status update), when using assign fields for mass updates and when saving analyzed data. Improved deletion of multiple links You can select multiple links using SHIFT or CTRL + select links before right-clicking to delete. You can delete links from the Logic Navigator window. You can delete links from the Rows section in the Home tab on the Ribbon menu. The delete option allow the user to filter on activities or link properties to make the proper link selection before deletion. Link Information View You may add additional columns to the predecessor or successor sections. You can also create layouts to save your column configuration in the link information view. You add columns or create layout by right-clicking in the predecessor or successor sections and choosing “Column lists”. Progress and Expended Added an option to filter on activities before loading the activities of the progress and expended window. Keyboard shortcut Added a keyboard shortcut, CTRL+Shift+U, to open the Userfields window when in the Data tab. Symbols We added a visual identifier to the symbols window frame if the layout is configured to use symbols from a different symbol set than the symbol set used by the project. ILAP We’ve added support for mapping of additional fields: Timenow, Start No Earlier Than, Actual Start, Actual Finish, Activity Type, Actual %, and Expended QTY.


7

Database changes Due to the performance work, there are some database changes. We have added:

• four new tables

• several temporary tables (only for Oracle).

We have changed:

• the primary key of sp_documents_links. We increased the space/size and added these columns

• extra_data of the rep_config table to allow 500 characters.

• added column extra_txt of the install_config table For more details, see chapter “Changes to the database definitions upgrading from v7.3.0”. For all details, see the database upgrade script named sqldb097.sql in the mss or ora catalog in the install directory.


8

Summary of Changes from 7.2 Safran Project is 64bit We have converted Safran Project from being a 32bit application to a 64bit application. Due to the change, Safran Project can only be installed in a 64bit Windows environment. The change needs the users to have the 64bit database clients installed. For technical details, see chapter Supported Environments. The install files are, by default, placed in C:\Program Files. Safran Project Personal - Local database is MS SQL Local DB We have changed the local database. Safran Project Personal installs MS SQL Local DB 2016 as the local database. For people upgrading from previous versions of Safran Project Personal, they should export the projects from their current local database before installing Safran Project 7.3, after installing Safran Project 7.3 they should import their projects into the MS SQL Local DB database. Safran Project *.ini file can be placed anywhere The safranpr.ini file can be placed anywhere on the local machine or a network share. To let Safran Project know where to look for the safranpr.ini file, the user needs to update the path inside the SafranConfig.xml file. You find the SafranConfig.xml file in Safran Project install directory. User Filter (DB Where Clause) We have implemented a User Filter. A User Filter is a filter in addition to the regular filter used in layouts and reports. So you can keep the filter saved with reports, and then add a user filter only to get a subset of the activities returned by the regular filter. Progress / Remaining Duration Added a feature to the Progress Import window. The feature allows the user to control how the import should deal with the situation where the imported Remaining Duration exceeds the duration. You can now choose to:

• Extend the Duration to match the Remaining Duration

• Truncate Remaining Duration to align with the Duration

• Don’t read the Remaining Duration in such instances. Cross-Project Links We have added a Cross Project Links feature when clicking Delete on the Home->Rows menu. When choosing Cross Project Links, you get a list of all the Cross Project Links from the current project to other projects. It can delete a cross-project link if you have update rights to both projects held together by the link.


9

Logic Navigator – Mass Delete of Links You can now select one or more links, using Shift or Ctrl, in the Predecessor/Successor field of the Logic Navigator. After making the selection, you can right-click on the Predecessor/Successor area and delete the selected links. Multiple Baselines in Reports The Histogram S Curve and the Barchart Editor Histogram now have an option to spread/stack on All Baselines. If a project has more than one Baseline, by using stack/spread on the bars/curves, you can see each baseline in your histograms visually. Histogram S Curve – Axix scaling You are now able to scale both the left and right Y-axis. By default, it displays the actual value, but you can choose it to be displayed in thousands or millions as well. You can configure this in the Histogram S-Curve Properties by choosing Report->Axis. Histogram S Curve – Legend displayed on a new page When using stack or spread, the number of colors or patterns can be substantial. In the Histogram S-Curve Properties Report->General, you can now choose Legend to be displayed on Extra Page. Performance Chart – Spread On We have added an option to use the Spread On function on cumulative lines in the Performance Chart. This enables the user to see the performance per userfield value. Bulls-Eye Report – Background picture It is now possible to add a background picture to the report. Add background pictures from the Report tab of the Bulls-Eye Properties window. Bulls-Eye Report – Multiple entries on one page It is now possible to draw lines in the Bulls-Eye report base on selected fields. To draw the lines, use Graph on from the Report tab of the Bulls-Eye Properties window.


10

Bulls-Eye and Bubble Chart Reports – Select Scope It is possible to choose which plan and scope to use and measure the SPI and CPI on. You can choose between Baseline, Current, Live, or Revised plan, and the scopes to choose from are Baseline, Current, Total, and User-defined. This is done from the Report tab of the Bulls Eye and Bubble Chart Properties windows. Bubble Chart – Single Projects It is now possible to use the Bubble Chart on single projects as well as on project groups. Bubble Chart – Multiple entries on one page It is possible to draw bubbles one selected fields (system and user-defined), in the Bubble Chart. This is done by using the Graph on from the Report tab of the Bubble Chart Properties window.


11

Issues fixed with 7.3.1 Build 119091 After installing this upgrade, you do also need to run a database upgrade and a recompile of triggers and procedures. For information about how to run the database upgrade and how to run a recompile of triggers and procedures, please see the “Installguide for Safran Project 7.3.0”. Barchart Editor:

Fixed an issue that caused drop-down lists to only display 3 list items when opened in a barchart editor column.

Fixed an issue where deleting an activity with the existing option is set to Non-Existence would cause an error.

Fixed an issue where fill down of Actual % could cause an error.

Barchart Editor Histogram:

Fixed an issue that would display the layout filter name in the header of an Editor Histogram.

Change Order:

Fixed an issue where moving resource items from one change order to and others could cause a loss of those resource items.

Export Project:

Fixed an issue where exporting to XER using resource aggregate wouldn’t aggregate the same type of resources in the XER file.

Filters:

Fixed an issue that, in some instances, didn't allow filtering on change orders.

ILAP:

Fixed an issue where one had to Open the Project with Exclusive access to be able to perform ILAP Export/Import. Now you can run ILAP Export/Import with Update access. Fixed an issue where Safran Project read incorrect values from Registry. Added a check that prevents users from importing existing activities into Safran Project, which in later imports could cause inconsistency and duplicate errors.


12

Import Project: Fixed an issue that prevented the import av budget numbers from an XML file into userfields of type Number.

Fixed an issue where you could experience a unique constraint error on outline codes when importing from XML.

Layouts:

Fixed an issue that could cause an error when a layout when using indentation on reference fields in a grouped layout.

Menus:

Added a keyboard shortcut, CTRL+Shift+U, to open the Userfields window when in the Data tab.

Project group:

Fixed an issue that would display activity sequence numbers instead of activity id in Link information view when looking at a cross-project link in a project group.

Fixed an issue that could cause an error when opening a Project Group containing several interface activities.

Fixed an issue that could cause an error when using local and inherited symbols with Project Groups

Report package:

Fixed an issue that prevented the progress bar to update when running a report package.

Reports:

Fixed an issue that prevented header text positioned upper left from displaying.

Fixed an issue that could cause a report to produce empty pages when stacking on outline codes.

Fixed an issue where a report pdf had different content from the print preview. The error is caused by configuring the symbol legend to display on a separate page.

Save As:

Fixed an issue where Enterprise field values didn't save when using Save As on a project.


13

Set status:

Fixed an issue where set status didn't calculate current plan progress for activities where the planned qty <0,01.

Fixed an issue that wrongly calculated Current Planned Progress to 100% on a Start Milestone where Early Start=Cutoff date.

Sys Adm:

Fixed an issue that would enable users to delete and transfer layouts and reports.


14

Issues fixed with 7.3.0 Build 119041 After installing this upgrade, you do also need to run a database upgrade and a recompile of triggers and procedures. For information about how to run the database upgrade and how to run a recompile of triggers and procedures, please see the “Installguide for Safran Project 7.3.0”. Baseline:

Fixed an issue that could cause a baseline change when using a resource profile with decimal values.

BE Histogram:

Fixed an issue where a filtered live plan would always end on 100%, while Baseline cum percent wouldn't end on 100%.

Fixed an issue that prevented curtains from being displayed correctly in projects with an hour based calendar.

BE Print:

Fixed row height validation. It validates if the row height is equal to the font size or higher.

Calendar Sets:

Fixed an issue that could cause the access tab of calendar sets to be disabled if the username had more than 15 characters.

Change Register:

Fixed an issue and made the Export to Excel visible in the Change Register.

Filter:

Fixed an issue that could cause an application terminates when using Auto Filter on Constraint dates.

Fixed a validation issue when using auto filter Forecast:

Fixed an issue that prevented the barchart editor from displaying forecast dates.

Histogram S-Curve:

Fixed an issue that prevented periodic live plan values from displaying in the Histogram S Curve table.


15

ILAP:

Fixed a resource error issue when using import include only specified mappings.

Fixed an activity error issue when using import include only specified mappings.

Fixed an issue that required Exclusive access to export, the minimum access level needed to export is now Update.

After installing Safran Project with ILAP, the registry path is the same as the one used by the ILAP adapter.

Information View:

Fixed an issue that could cause undocked Information views to crash.

Integrated Plan:

Fixed an issue that causes a double set of value mappings.

Fixed an internal transfer issue that didn't display a value list when selecting default mapping value. Fixed a missing refresh when changing the mapping method.

Partial Baseline:

Fixed a filter issue used by the partial baseline function.

Fixed an issue that didn't update Baseline QTY Cost when running a partial baseline.

Project Export:

We improved our Export XML format. The network analysis is more aligned between Safran Project and MS Project when importing the Safran Project exported XML file into MS Project.

Project Import:

Fixed an issue where import->update of a Project would overwrite the Flag field label of the Deleted flag field.

Project Properties:

Fixed an issue that caused Progress Update Methods from being displayed in Project Properties.


16

Report Packages: Fixed an issue that excludes the report filter when using the filter in combination with a report package filter.

Made adjustments to improve performance when using R field

iterations on report packages. Reports:

Fixed an issue that didn’t display <Cut-off> date when used in report headers.

Fixed an issue that prevented global value <Report Name> from being displayed in report headers.

Resource View:

Fixed an issue that prevented total allocated resources from being displayed correctly.

Fixed an issue that prevented resource history from being displayed when using Oracle. Fixed an issue that could cause an error when using a resource histogram set up as bi-weekly on a multi-shift project.

Project:

Fixed an issue that prevented saving a project when a user had a different access level to the sub-projects.

Spooler:

Fixed an issue where spooler generated reports didn't reflect updated information.

Fixed an issue that could cause a spooler histogram to look different from the report in Safran Project.

Symbols:

Fixed an issue that could cause the necked summary bar to draw incorrectly.

Userfield Sets: Fixed an issue that could cause a code retrieval error when using a

linked userfield set.


17

Changes to database definitions upgrading from v7.3.0 if object_id( 'tr_profile_intv_insert') is not null drop TRIGGER tr_profile_intv_insert ; if object_id( 'tr_profile_intv_delete') is not null drop TRIGGER tr_profile_intv_delete ; ALTER TABLE sp_document_links DROP CONSTRAINT pk_doc_links ; alter table sp_document_links alter column label varchar(255) NOT NULL ; ALTER TABLE sp_document_links ADD CONSTRAINT pk_doc_links PRIMARY KEY (seq, net_id, label) ; alter table sp_document_links add status int null ; CREATE TABLE activities_save (

proc_id int NOT NULL , seq int NOT NULL, pc float NULL , rdu integer NULL, hammock int NULL, an varchar(100) NULL, des varchar(1000) NULL, du int NULL , tse datetime NULL , tsl datetime NULL , tce datetime NULL , tcl datetime NULL , fsd datetime NULL , ffd datetime NULL , acs datetime NULL , acf datetime NULL , es datetime NULL , ef datetime NULL , ls datetime NULL , lf datetime NULL , tf int NULL , ff int NULL , net_id int NOT NULL , d1 datetime NULL , d2 datetime NULL , d3 datetime NULL , d4 datetime NULL , n1 float NULL , n2 float NULL , n3 float NULL , n4 float NULL ,


18

n11 float NULL , n12 float NULL , n13 float NULL , n14 float NULL , current_progress float NULL , frontline_date datetime NULL , d5 datetime NULL , d6 datetime NULL , d7 datetime NULL , d8 datetime NULL , original_qty float NULL , approved_vo_qty float NULL , estimated_vo_qty float NULL , subcontr_vo_qty float NULL , internal_vo_qty float NULL , jobpack_est_qty float NULL , expended_qty float NULL , esa datetime NULL , current_planned_prog float NULL , base_planned_prog float NULL , oes datetime NULL , oef datetime NULL , ols datetime NULL , olf datetime NULL , bes datetime NULL , besa datetime NULL , bef datetime NULL , bls datetime NULL , blf datetime NULL , ces datetime NULL , cef datetime NULL , cls datetime NULL , clf datetime NULL , original_qty1 float NULL , csh float NULL , rsh float NULL , tsh float NULL , curr_frontline_date datetime NULL , ess datetime NULL , efs datetime NULL , tfs int NULL , ffs int NULL , manual_prog_flag smallint NULL , current_pc float NULL , rdua int NULL , cesa datetime NULL , ctf int NULL , cff int NULL , loos tinyint NULL , coos tinyint NULL , out_of_sync tinyint NULL ,


19

d9 datetime NULL , d10 datetime NULL , d11 datetime NULL , d12 datetime NULL , d13 datetime NULL , d14 datetime NULL , d15 datetime NULL , d16 datetime NULL , d17 datetime NULL , d18 datetime NULL , d19 datetime NULL , d20 datetime NULL , n5 float NULL , n6 float NULL , n7 float NULL , n8 float NULL , n9 float NULL , n10 float NULL , n15 float NULL , n16 float NULL , n17 float NULL , n18 float NULL , n19 float NULL , n20 float NULL , l1 tinyint NULL , l2 tinyint NULL , l3 tinyint NULL , l4 tinyint NULL , l5 tinyint NULL , l6 tinyint NULL , l7 tinyint NULL , l8 tinyint NULL , l9 tinyint NULL , l10 tinyint NULL , l11 tinyint NULL , l12 tinyint NULL , l13 tinyint NULL , l14 tinyint NULL , l15 tinyint NULL , l16 tinyint NULL , l17 tinyint NULL , l18 tinyint NULL , l19 tinyint NULL , l20 tinyint NULL , fcdu int NULL , fcesa datetime NULL , fcef datetime NULL , resa datetime NULL , res datetime NULL , ref datetime NULL , rls datetime NULL ,


20

rlf datetime NULL , rev_frontline_date datetime NULL , revised_planned_prog float NULL , fcqty float NULL , dur_fmt tinyint NULL , row_no int NULL , outline_level tinyint NULL , link_summary int NULL , cpc float NULL , rev_scope float NULL , u1 varchar(10) NULL , u2 varchar(10) NULL , u3 varchar(10) NULL , u4 varchar(10) NULL , u5 varchar(10) NULL , u6 varchar(10) NULL , u7 varchar(10) NULL , u8 varchar(10) NULL , u9 varchar(10) NULL , u10 varchar(10) NULL , min_dur int NULL , act_exi tinyint NULL , act_fit tinyint NULL , alap tinyint NULL , act_type smallint NULL , look_ahead int NULL , d21 datetime NULL , d22 datetime NULL , d23 datetime NULL , d24 datetime NULL , d25 datetime NULL , d26 datetime NULL , d27 datetime NULL , d28 datetime NULL , d29 datetime NULL , d30 datetime NULL , d31 datetime NULL , d32 datetime NULL , d33 datetime NULL , d34 datetime NULL , d35 datetime NULL , d36 datetime NULL , d37 datetime NULL , d38 datetime NULL , d39 datetime NULL , d40 datetime NULL , current_rdu int NULL , esas datetime NULL , jobflag int NULL, on_target int NULL, evm_method varchar(10) NULL,


21

current_as datetime NULL , current_af datetime NULL , CONSTRAINT pk_activities_save PRIMARY KEY CLUSTERED (proc_id, seq, net_id))

; grant all on activities_save to powerplan ; create table activity_texts_save ( proc_id integer not null, seq integer not null, net_id integer not null, field_nr smallint not null, field_value varchar(1000) null, constraint pk_act_texts_save Primary key (proc_id, net_id, seq, field_nr )) ; grant all on activity_texts_save to powerplan ; create table act_impact_save ( proc_id integer not null, an_seq integer not null, net_id integer not null, set_nr integer not null, du integer null, dur_fmt tinyint null, act_exist tinyint null, esa datetime null, es datetime null, ef datetime null, ls datetime null, lf datetime null, tf integer null, ff integer null, wpn integer null, constraint pk_act_impact_save Primary key (proc_id, net_id, an_seq, set_nr)) ; grant all on act_impact_save to powerplan ; CREATE TABLE rap_act_load (

user_id int NOT NULL , seq int NOT NULL , net_id int NOT NULL , extra int NOT NULL, CONSTRAINT pk_rap_act_load PRIMARY KEY CLUSTERED (user_id, seq, net_id,

extra)) ; grant all on rap_act_load to powerplan ;


22

ALTER TABLE rep_config ALTER COLUMN extra_data varchar(500) ; /*..procedures that can be removed drop procedure prc_enter_dates ; drop procedure prc_enter_dates_h ; drop procedure prc_enter_dates_m ; drop procedure prc_enter_rowdata ; drop procedure prc_enter_impact_dates ; drop procedure prc_enter_impact_dates_h ; drop procedure prc_enter_impact_dates_m ; drop procedure prc_save_userf_texts ; drop procedure prc_enter_curdat ; drop procedure prc_enter_curdat_h ; drop procedure prc_enter_curdat_m ; drop procedure prc_enter_fcdates ; drop procedure prc_enter_fcdates_h ; drop procedure prc_enter_fcdates_m ; drop procedure prc_enter_risk_px ; drop procedure prc_enter_risk_px_h ; drop procedure prc_enter_risk_px_m ; drop procedure prc_bl_upd_act_leveled ; drop procedure prc_bl_upd_act ; drop procedure prc_su_upd_peri ; */ alter table install_config add extra_txt nvarchar(50) null ; delete from user_locking ;


23

INSERT into version VALUES ( 97, '7.3.1', 'Enterprise Edition', '2019.09.01 00:00:00', 'New Version' ) ; ;


24

Changes to database definitions upgrading from v7.2 alter table period_status_a add current_rdu int null ; alter table activities add current_rdu int null ; alter table baseline_a add current_rdu int null ; alter table forecast_data add current_rdu int null ; ALTER TABLE profile_intv DROP CONSTRAINT pk_profile_intv ; ALTER TABLE profile_intv ALTER COLUMN value_x float NOT NULL ; ALTER TABLE profile_intv ALTER COLUMN value_y float NOT NULL ; ALTER TABLE profile_intv ADD CONSTRAINT pk_profile_intv PRIMARY KEY CLUSTERED ( profile_id ASC, profileset_id ASC, value_x ASC ) ; alter table activities add esas datetime null ; alter table baseline_log add plan_type int null ; update baseline_log set plan_type = 0 ; alter table mp_member add cal_no int null ; alter table mp_member add profile_no int null ; alter table mp_master alter column logo1 varchar(250) ; alter table mp_master alter column logo2 varchar(250) ; alter table project_config alter column logo_bmp varchar(250) ; alter table project_config alter column client_bmp varchar(250) ; alter table cross_plan_links alter column lag_fmt tinyint ;


25

alter table ilap_exchange_config drop constraint fk_ilap_exchange_config_subnet ; alter table ilap_exchange_config drop constraint fk_ilap_exchange_config_ufset ; alter table pt_act_grids alter column grid_text varchar(50) ; alter table edit_hist_grids alter column grid_text varchar(50) ; alter table ptavle_grids alter column grid_text varchar(50) ; alter table rep_groups alter column group_name varchar(25) ; ALTER TABLE prj_pers DROP CONSTRAINT pk_prj_pers ; ALTER TABLE prj_pers ADD CONSTRAINT pk_prj_pers PRIMARY KEY CLUSTERED ( prj_pid ASC, prj_sign ASC ) ; INSERT into version VALUES ( 96, '7.3', 'Enterprise Edition', '2018.07.01 00:00:00', 'New Version' ) ;


26

Documentation At the time of releasing Safran Project 7.3.0, the following documentation is available:

• Exploring Safran Project 7.3

• Safran Project 7.3 Quick Start

• Installguide for Safran Project 7.3

• Customer Release Note for Safran Project 7.3

• Exploring Safran ILAP

Supported Environments

Recommended Minimum

Operating systems Windows 10 64bit

Windows 7 64bit

Processor 2Ghz or higher 2Ghz

Memory (RAM) 8GB 4GB

Disk Space (for local installations)

250MB 250M

Microsoft .Net Framework

4.5 4.5

Safran Project 7.3 supports the following database management:

MS SQL Server 2012, 2014, 2016

Oracle 12c

For MS SQL Server you should use MS SQL Native client 2012

Use the 64bit version of Oracle and MS SQL Native Client.


27

Technical Support If you have any issues with Safran Project, please report them to Safran Software Solutions AS. You can send us a “ticket” from inside the software. If you right-click on the menu line and choose “Support,” the program opens a new email dialogue with our address filled in. Please write a proper subject heading and description, providing details of your issue and what you did before the situation and send it to us. The email registers as a ticket in our support system. Obtain Technical support for Safran Project from: Safran Software Solutions AS Postbox 8118, N-4068 Stavanger, Norway Phone: +47 40 00 47 07,

E-mail: [email protected] Web: http://support.safran.com

Customer Release Notesdownload.safran.no/Download/Doc/Project/ver731/CRN... · Safran Project 7.3.1 needs an upgraded database. The Safran Project database needs to be version 7.3.1.

Documents