FIDAB is a product and document management system. It handles products and hierarchies of products and tracks product releases. Products are defined by documents, which are put under revision control.
Be the first to post a text review of FIDAB PDM. Rate and review a project by clicking thumbs up or thumbs down in the right column.
R5C Corrected syntax error in dba.sql. Corrected mixup of fields when creating new documents. Made document title field not editable when locked. R5B New property DEFAULT_MAIL_DOMAIN in Fidab.ini. It is used to complete mail addresses in Fidab without an '@'. A new menu 'Settings' is added and populated with items from the About menu. A new setting for the file archive is added to the Settings menu. It makes it possible to override the viewer assigned to file formats and instead use Windows' mechanism to locate a suitable program using the file extension. R5A The database schema is modified. Run sql/postgresql/update_dba_R5.sql or sql/oracle/update_dba_R5.sql to update an existing database. Use sql/postgresql/update_dba_R5_psql7.sql for PostgreSQL version < 8. Bill of Materials - The multiplicity of a configuration included in a parent configuration can be given. The quantity defaults to 1 for existing configurations. The quantity is also printed on Configuration2Report. Selectable numbering schemes for revisions and configuration are included. The desired numbering scheme is selected with VERSION_MANAGER in Fidab.ini. Set VERSION_MANAGER=se.fyrplus.fidab.client.FyrplusVersionManager for the standard numbering scheme and use se.fyrplus.fidab.client.TietoEnatorVersionManager for the new numbering scheme. It is now possible to have individual login names and passwords for each user of Fidab. If you set DATABASE_USER= and DATABASE_PASSWORD= in Fidab.ini, a login prompt will be shown when Fidab starts. A sample SQL file is given to create three roles in the database; fidabadmin, fidabwriter and fidabviewer. These can be used to control what a user is allowed to change in the database. The file is called sql/postgresql/Fidab_SQL_Roles.sql. The product name field accepts up to 50 characters. A title field is added to Documents. It is possible to select if the document title or the document type should be displayed in the tree. Set DOCUMENT_NAME_IN_TREE=type in Fidab.ini to display the type, or DOCUMENT_NAME_IN_TREE=title to display the title. R4E Enabled use of lower to uppercase conversion in textfields constrained with regexp, aka product class fields. A new optional parameter PRODUCT_CLASS_CASE added. Corrected company label in report footer. R4D Fixed bug in file archive name/type/viewable sort order. R4C Added possibility to create pdf reports in Fidab. It is possible to add your own reports by adding the class name in fidab.ini and then implement a report and inherit from base class Reports.java. The reports are created in the users temporary directory and shown with the command in the fidab.ini. R4B When multiple operating systems were used simultaneously, Fidab could sometimes fail to list all FileTypes. This is fixed. File suffixes are made case insensitive. $HOME can be used in filearchive storage paths. R4A It is now possible to configure the length and syntax of product class names. However, note that with this new feature the database design has been changed and utilizing the new feature on an existing fidab installation will require manual non-simple database manipulation. More specifically the data type of the column 'code' of the table 'ProductClass' table will have to be chaged to varchar(80) for Postgres and varchar2(80) for Oracle. No error message is displayed if Fidab can't suggest the new revision number in the dialog for New revision. Instead the revision number suggestion combo box is empty and a new revision number has to be entered manually. The user manual has been updated to reflect the current functionality of Fidab. A bug in the mail notification code that appears from version R3D (the file URL is missing) has been fixed. A bug in the dba.sql scripts that appears from version R3D (the table creation order is not compliant with the internal dependencies among the tables) has been fixed. R3D Connects each document type with a document revision acting as the template for the document type. When a new document is created the template for it can be downloaded. Automatically suggests the file type of a new file archive revision by looking at the suffix of the file name if there is one. Admin dialog for file types extended accordingly to bind file types and file suffixes. R3C Searches in database made with lowercase strings instead of uppercase strings to work around a bug with swedish characters in PostgreSQL. Better sorting of documents and products. R3B Physical archive fixed to accept backslash. R3A It is possible to modify filetype and viewstatus for a revision after creation. It is possible to filter what revisions are displayed in the tree. It is possible for a user to reserve a document for exclusive modification. This requires a new table in the database if you are upgrading from an eariler version. Directory selection for copy file command works as expected. It is possible to disconnect subproducts, even when they are part of a configuration. Already existing configurations are kept intact. 1Mb copy buffer for files. New unique constraint for accessdirectory table. Fixed double backslash bug for PostgreSQL. Write protect revision directories in file archive. Removed unnecessary prints. R2J Removed ordering of archive names. R2I Requires java.util.regexp in JDK1.4. New numbering scheme for configurations. It is now possible to create configurations with unlocked member configurations. It is not possible to lock a configuration with unlocked member configurations. Sorting classes, series, viewers and types before displaying them. R2H Correct resource tag for VIEWER_COLUMN in File type dialog. R2G Correct text on 'Save' button in administration dialog. R2F Files Oracle.class and PostgreSQL.class are included in the jar file. Message for broken next configuration code moved to status bar. Rearranged the Fidab.ini file. Added postgresql.jar to testfidab.cmd. Recommended use of UNICODE with PostgreSQL. PostgreSQL 7.x is required. New configuration option for socket connections in PostgreSQL.
R5C Corrected syntax error in dba.sql. Corrected mixup of fields when creating new documents. Made document title field not editable when locked. R5B New property DEFAULT_MAIL_DOMAIN in Fidab.ini. It is used to complete mail addresses in Fidab without an '@'. A new menu 'Settings' is added and populated with items from the About menu. A new setting for the file archive is added to the Settings menu. It makes it possible to override the viewer assigned to file formats and instead use Windows' mechanism to locate a suitable program using the file extension. R5A The database schema is modified. Run sql/postgresql/update_dba_R5.sql or sql/oracle/update_dba_R5.sql to update an existing database. Use sql/postgresql/update_dba_R5_psql7.sql for PostgreSQL version < 8. Bill of Materials - The multiplicity of a configuration included in a parent configuration can be given. The quantity defaults to 1 for existing configurations. The quantity is also printed on Configuration2Report. Selectable numbering schemes for revisions and configuration are included. The desired numbering scheme is selected with VERSION_MANAGER in Fidab.ini. Set VERSION_MANAGER=se.fyrplus.fidab.client.FyrplusVersionManager for the standard numbering scheme and use se.fyrplus.fidab.client.TietoEnatorVersionManager for the new numbering scheme. It is now possible to have individual login names and passwords for each user of Fidab. If you set DATABASE_USER= and DATABASE_PASSWORD= in Fidab.ini, a login prompt will be shown when Fidab starts. A sample SQL file is given to create three roles in the database; fidabadmin, fidabwriter and fidabviewer. These can be used to control what a user is allowed to change in the database. The file is called sql/postgresql/Fidab_SQL_Roles.sql. The product name field accepts up to 50 characters. A title field is added to Documents. It is possible to select if the document title or the document type should be displayed in the tree. Set DOCUMENT_NAME_IN_TREE=type in Fidab.ini to display the type, or DOCUMENT_NAME_IN_TREE=title to display the title. R4E Enabled use of lower to uppercase conversion in textfields constrained with regexp, aka product class fields. A new optional parameter PRODUCT_CLASS_CASE added. Corrected company label in report footer. R4D Fixed bug in file archive name/type/viewable sort order. R4C Added possibility to create pdf reports in Fidab. It is possible to add your own reports by adding the class name in fidab.ini and then implement a report and inherit from base class Reports.java. The reports are created in the users temporary directory and shown with the command in the fidab.ini. R4B When multiple operating systems were used simultaneously, Fidab could sometimes fail to list all FileTypes. This is fixed. File suffixes are made case insensitive. $HOME can be used in filearchive storage paths. R4A It is now possible to configure the length and syntax of product class names. However, note that with this new feature the database design has been changed and utilizing the new feature on an existing fidab installation will require manual non-simple database manipulation. More specifically the data type of the column 'code' of the table 'ProductClass' table will have to be chaged to varchar(80) for Postgres and varchar2(80) for Oracle. No error message is displayed if Fidab can't suggest the new revision number in the dialog for New revision. Instead the revision number suggestion combo box is empty and a new revision number has to be entered manually. The user manual has been updated to reflect the current functionality of Fidab. A bug in the mail notification code that appears from version R3D (the file URL is missing) has been fixed. A bug in the dba.sql scripts that appears from version R3D (the table creation order is not compliant with the internal dependencies among the tables) has been fixed. R3D Connects each document type with a document revision acting as the template for the document type. When a new document is created the template for it can be downloaded. Automatically suggests the file type of a new file archive revision by looking at the suffix of the file name if there is one. Admin dialog for file types extended accordingly to bind file types and file suffixes. R3C Searches in database made with lowercase strings instead of uppercase strings to work around a bug with swedish characters in PostgreSQL. Better sorting of documents and products. R3B Physical archive fixed to accept backslash. R3A It is possible to modify filetype and viewstatus for a revision after creation. It is possible to filter what revisions are displayed in the tree. It is possible for a user to reserve a document for exclusive modification. This requires a new table in the database if you are upgrading from an eariler version. Directory selection for copy file command works as expected. It is possible to disconnect subproducts, even when they are part of a configuration. Already existing configurations are kept intact. 1Mb copy buffer for files. New unique constraint for accessdirectory table. Fixed double backslash bug for PostgreSQL. Write protect revision directories in file archive. Removed unnecessary prints. R2J Removed ordering of archive names. R2I Requires java.util.regexp in JDK1.4. New numbering scheme for configurations. It is now possible to create configurations with unlocked member configurations. It is not possible to lock a configuration with unlocked member configurations. Sorting classes, series, viewers and types before displaying them. R2H Correct resource tag for VIEWER_COLUMN in File type dialog. R2G Correct text on 'Save' button in administration dialog. R2F Files Oracle.class and PostgreSQL.class are included in the jar file. Message for broken next configuration code moved to status bar. Rearranged the Fidab.ini file. Added postgresql.jar to testfidab.cmd. Recommended use of UNICODE with PostgreSQL. PostgreSQL 7.x is required. New configuration option for socket connections in PostgreSQL.
R5A The database schema is modified. Run sql/postgresql/update_dba_R5.sql or sql/oracle/update_dba_R5.sql to update an existing database. Use sql/postgresql/update_dba_R5_psql7.sql for PostgreSQL version < 8. Bill of Materials - The multiplicity of a configuration included in a parent configuration can be given. The quantity defaults to 1 for existing configurations. The quantity is also printed on Configuration2Report. Selectable numbering schemes for revisions and configuration are included. The desired numbering scheme is selected with VERSION_MANAGER in Fidab.ini. Set VERSION_MANAGER=se.fyrplus.fidab.client.FyrplusVersionManager for the standard numbering scheme and use se.fyrplus.fidab.client.TietoEnatorVersionManager for the new numbering scheme. It is now possible to have individual login names and passwords for each user of Fidab. If you set DATABASE_USER= and DATABASE_PASSWORD= in Fidab.ini, a login prompt will be shown when Fidab starts. A sample SQL file is given to create three roles in the database; fidabadmin, fidabwriter and fidabviewer. These can be used to control what a user is allowed to change in the database. The file is called sql/postgresql/Fidab_SQL_Roles.sql. The product name field accepts up to 50 characters. A title field is added to Documents. It is possible to select if the document title or the document type should be displayed in the tree. Set DOCUMENT_NAME_IN_TREE=type in Fidab.ini to display the type, or DOCUMENT_NAME_IN_TREE=title to display the title. R4E Enabled use of lower to uppercase conversion in textfields constrained with regexp, aka product class fields. A new optional parameter PRODUCT_CLASS_CASE added. Corrected company label in report footer. R4D Fixed bug in file archive name/type/viewable sort order. R4C Added possibility to create pdf reports in Fidab. It is possible to add your own reports by adding the class name in fidab.ini and then implement a report and inherit from base class Reports.java. The reports are created in the users temporary directory and shown with the command in the fidab.ini. R4B When multiple operating systems were used simultaneously, Fidab could sometimes fail to list all FileTypes. This is fixed. File suffixes are made case insensitive. $HOME can be used in filearchive storage paths. R4A It is now possible to configure the length and syntax of product class names. However, note that with this new feature the database design has been changed and utilizing the new feature on an existing fidab installation will require manual non-simple database manipulation. More specifically the data type of the column 'code' of the table 'ProductClass' table will have to be chaged to varchar(80) for Postgres and varchar2(80) for Oracle. No error message is displayed if Fidab can't suggest the new revision number in the dialog for New revision. Instead the revision number suggestion combo box is empty and a new revision number has to be entered manually. The user manual has been updated to reflect the current functionality of Fidab. A bug in the mail notification code that appears from version R3D (the file URL is missing) has been fixed. A bug in the dba.sql scripts that appears from version R3D (the table creation order is not compliant with the internal dependencies among the tables) has been fixed. R3D Connects each document type with a document revision acting as the template for the document type. When a new document is created the template for it can be downloaded. Automatically suggests the file type of a new file archive revision by looking at the suffix of the file name if there is one. Admin dialog for file types extended accordingly to bind file types and file suffixes. R3C Searches in database made with lowercase strings instead of uppercase strings to work around a bug with swedish characters in PostgreSQL. Better sorting of documents and products. R3B Physical archive fixed to accept backslash. R3A It is possible to modify filetype and viewstatus for a revision after creation. It is possible to filter what revisions are displayed in the tree. It is possible for a user to reserve a document for exclusive modification. This requires a new table in the database if you are upgrading from an eariler version. Directory selection for copy file command works as expected. It is possible to disconnect subproducts, even when they are part of a configuration. Already existing configurations are kept intact. 1Mb copy buffer for files. New unique constraint for accessdirectory table. Fixed double backslash bug for PostgreSQL. Write protect revision directories in file archive. Removed unnecessary prints. R2J Removed ordering of archive names. R2I Requires java.util.regexp in JDK1.4. New numbering scheme for configurations. It is now possible to create configurations with unlocked member configurations. It is not possible to lock a configuration with unlocked member configurations. Sorting classes, series, viewers and types before displaying them. R2H Correct resource tag for VIEWER_COLUMN in File type dialog. R2G Correct text on 'Save' button in administration dialog. R2F Files Oracle.class and PostgreSQL.class are included in the jar file. Message for broken next configuration code moved to status bar. Rearranged the Fidab.ini file. Added postgresql.jar to testfidab.cmd. Recommended use of UNICODE with PostgreSQL. PostgreSQL 7.x is required. New configuration option for socket connections in PostgreSQL.
R5A The database schema is modified. Run sql/postgresql/update_dba_R5.sql or sql/oracle/update_dba_R5.sql to update an existing database. Use sql/postgresql/update_dba_R5_psql7.sql for PostgreSQL version < 8. Bill of Materials - The multiplicity of a configuration included in a parent configuration can be given. The quantity defaults to 1 for existing configurations. The quantity is also printed on Configuration2Report. Selectable numbering schemes for revisions and configuration are included. The desired numbering scheme is selected with VERSION_MANAGER in Fidab.ini. Set VERSION_MANAGER=se.fyrplus.fidab.client.FyrplusVersionManager for the standard numbering scheme and use se.fyrplus.fidab.client.TietoEnatorVersionManager for the new numbering scheme. It is now possible to have individual login names and passwords for each user of Fidab. If you set DATABASE_USER= and DATABASE_PASSWORD= in Fidab.ini, a login prompt will be shown when Fidab starts. A sample SQL file is given to create three roles in the database; fidabadmin, fidabwriter and fidabviewer. These can be used to control what a user is allowed to change in the database. The file is called sql/postgresql/Fidab_SQL_Roles.sql. The product name field accepts up to 50 characters. A title field is added to Documents. It is possible to select if the document title or the document type should be displayed in the tree. Set DOCUMENT_NAME_IN_TREE=type in Fidab.ini to display the type, or DOCUMENT_NAME_IN_TREE=title to display the title. R4E Enabled use of lower to uppercase conversion in textfields constrained with regexp, aka product class fields. A new optional parameter PRODUCT_CLASS_CASE added. Corrected company label in report footer. R4D Fixed bug in file archive name/type/viewable sort order. R4C Added possibility to create pdf reports in Fidab. It is possible to add your own reports by adding the class name in fidab.ini and then implement a report and inherit from base class Reports.java. The reports are created in the users temporary directory and shown with the command in the fidab.ini. R4B When multiple operating systems were used simultaneously, Fidab could sometimes fail to list all FileTypes. This is fixed. File suffixes are made case insensitive. $HOME can be used in filearchive storage paths. R4A It is now possible to configure the length and syntax of product class names. However, note that with this new feature the database design has been changed and utilizing the new feature on an existing fidab installation will require manual non-simple database manipulation. More specifically the data type of the column 'code' of the table 'ProductClass' table will have to be chaged to varchar(80) for Postgres and varchar2(80) for Oracle. No error message is displayed if Fidab can't suggest the new revision number in the dialog for New revision. Instead the revision number suggestion combo box is empty and a new revision number has to be entered manually. The user manual has been updated to reflect the current functionality of Fidab. A bug in the mail notification code that appears from version R3D (the file URL is missing) has been fixed. A bug in the dba.sql scripts that appears from version R3D (the table creation order is not compliant with the internal dependencies among the tables) has been fixed. R3D Connects each document type with a document revision acting as the template for the document type. When a new document is created the template for it can be downloaded. Automatically suggests the file type of a new file archive revision by looking at the suffix of the file name if there is one. Admin dialog for file types extended accordingly to bind file types and file suffixes. R3C Searches in database made with lowercase strings instead of uppercase strings to work around a bug with swedish characters in PostgreSQL. Better sorting of documents and products. R3B Physical archive fixed to accept backslash. R3A It is possible to modify filetype and viewstatus for a revision after creation. It is possible to filter what revisions are displayed in the tree. It is possible for a user to reserve a document for exclusive modification. This requires a new table in the database if you are upgrading from an eariler version. Directory selection for copy file command works as expected. It is possible to disconnect subproducts, even when they are part of a configuration. Already existing configurations are kept intact. 1Mb copy buffer for files. New unique constraint for accessdirectory table. Fixed double backslash bug for PostgreSQL. Write protect revision directories in file archive. Removed unnecessary prints. R2J Removed ordering of archive names. R2I Requires java.util.regexp in JDK1.4. New numbering scheme for configurations. It is now possible to create configurations with unlocked member configurations. It is not possible to lock a configuration with unlocked member configurations. Sorting classes, series, viewers and types before displaying them. R2H Correct resource tag for VIEWER_COLUMN in File type dialog. R2G Correct text on 'Save' button in administration dialog. R2F Files Oracle.class and PostgreSQL.class are included in the jar file. Message for broken next configuration code moved to status bar. Rearranged the Fidab.ini file. Added postgresql.jar to testfidab.cmd. Recommended use of UNICODE with PostgreSQL. PostgreSQL 7.x is required. New configuration option for socket connections in PostgreSQL.
R4C Added possibility to create pdf reports in Fidab. It is possible to add your own reports by adding the class name in fidab.ini and then implement a report and inherit from base class Reports.java. The reports are created in the users temporary directory and shown with the command in the fidab.ini. R4B When multiple operating systems were used simultaneously, Fidab could sometimes fail to list all FileTypes. This is fixed. File suffixes are made case insensitive. $HOME can be used in filearchive storage paths. R4A It is now possible to configure the length and syntax of product class names. However, note that with this new feature the database design has been changed and utilizing the new feature on an existing fidab installation will require manual non-simple database manipulation. More specifically the data type of the column 'code' of the table 'ProductClass' table will have to be chaged to varchar(80) for Postgres and varchar2(80) for Oracle. No error message is displayed if Fidab can't suggest the new revision number in the dialog for New revision. Instead the revision number suggestion combo box is empty and a new revision number has to be entered manually. The user manual has been updated to reflect the current functionality of Fidab. A bug in the mail notification code that appears from version R3D (the file URL is missing) has been fixed. A bug in the dba.sql scripts that appears from version R3D (the table creation order is not compliant with the internal dependencies among the tables) has been fixed. R3D Connects each document type with a document revision acting as the template for the document type. When a new document is created the template for it can be downloaded. Automatically suggests the file type of a new file archive revision by looking at the suffix of the file name if there is one. Admin dialog for file types extended accordingly to bind file types and file suffixes. R3C Searches in database made with lowercase strings instead of uppercase strings to work around a bug with swedish characters in PostgreSQL. Better sorting of documents and products. R3B Physical archive fixed to accept backslash. R3A It is possible to modify filetype and viewstatus for a revision after creation. It is possible to filter what revisions are displayed in the tree. It is possible for a user to reserve a document for exclusive modification. This requires a new table in the database if you are upgrading from an eariler version. Directory selection for copy file command works as expected. It is possible to disconnect subproducts, even when they are part of a configuration. Already existing configurations are kept intact. 1Mb copy buffer for files. New unique constraint for accessdirectory table. Fixed double backslash bug for PostgreSQL. Write protect revision directories in file archive. Removed unnecessary prints. R2J Removed ordering of archive names. R2I Requires java.util.regexp in JDK1.4. New numbering scheme for configurations. It is now possible to create configurations with unlocked member configurations. It is not possible to lock a configuration with unlocked member configurations. Sorting classes, series, viewers and types before displaying them. R2H Correct resource tag for VIEWER_COLUMN in File type dialog. R2G Correct text on 'Save' button in administration dialog. R2F Files Oracle.class and PostgreSQL.class are included in the jar file. Message for broken next configuration code moved to status bar. Rearranged the Fidab.ini file. Added postgresql.jar to testfidab.cmd. Recommended use of UNICODE with PostgreSQL. PostgreSQL 7.x is required. New configuration option for socket connections in PostgreSQL.
R4C Added possibility to create pdf reports in Fidab. It is possible to add your own reports by adding the class name in fidab.ini and then implement a report and inherit from base class Reports.java. The reports are created in the users temporary directory and shown with the command in the fidab.ini. R4B When multiple operating systems were used simultaneously, Fidab could sometimes fail to list all FileTypes. This is fixed. File suffixes are made case insensitive. $HOME can be used in filearchive storage paths. R4A It is now possible to configure the length and syntax of product class names. However, note that with this new feature the database design has been changed and utilizing the new feature on an existing fidab installation will require manual non-simple database manipulation. More specifically the data type of the column 'code' of the table 'ProductClass' table will have to be chaged to varchar(80) for Postgres and varchar2(80) for Oracle. No error message is displayed if Fidab can't suggest the new revision number in the dialog for New revision. Instead the revision number suggestion combo box is empty and a new revision number has to be entered manually. The user manual has been updated to reflect the current functionality of Fidab. A bug in the mail notification code that appears from version R3D (the file URL is missing) has been fixed. A bug in the dba.sql scripts that appears from version R3D (the table creation order is not compliant with the internal dependencies among the tables) has been fixed. R3D Connects each document type with a document revision acting as the template for the document type. When a new document is created the template for it can be downloaded. Automatically suggests the file type of a new file archive revision by looking at the suffix of the file name if there is one. Admin dialog for file types extended accordingly to bind file types and file suffixes. R3C Searches in database made with lowercase strings instead of uppercase strings to work around a bug with swedish characters in PostgreSQL. Better sorting of documents and products. R3B Physical archive fixed to accept backslash. R3A It is possible to modify filetype and viewstatus for a revision after creation. It is possible to filter what revisions are displayed in the tree. It is possible for a user to reserve a document for exclusive modification. This requires a new table in the database if you are upgrading from an eariler version. Directory selection for copy file command works as expected. It is possible to disconnect subproducts, even when they are part of a configuration. Already existing configurations are kept intact. 1Mb copy buffer for files. New unique constraint for accessdirectory table. Fixed double backslash bug for PostgreSQL. Write protect revision directories in file archive. Removed unnecessary prints. R2J Removed ordering of archive names. R2I Requires java.util.regexp in JDK1.4. New numbering scheme for configurations. It is now possible to create configurations with unlocked member configurations. It is not possible to lock a configuration with unlocked member configurations. Sorting classes, series, viewers and types before displaying them. R2H Correct resource tag for VIEWER_COLUMN in File type dialog. R2G Correct text on 'Save' button in administration dialog. R2F Files Oracle.class and PostgreSQL.class are included in the jar file. Message for broken next configuration code moved to status bar. Rearranged the Fidab.ini file. Added postgresql.jar to testfidab.cmd. Recommended use of UNICODE with PostgreSQL. PostgreSQL 7.x is required. New configuration option for socket connections in PostgreSQL.
Be the first person to add a text review.
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?
Thanks for your review!
Get credit for your review by logging in via OpenID. Click your account provider: