I was wondering about what idea was behind the naming scheme for the form backup file-names. For me, it would be more useful if the naming scheme was along the lines of:
[product-name-and-version]_[form-name]_[site]_[date].[ext]
A backup I made today was named this:
CFV5_FormsBackup_ON_http---www.globalpittsburgh.org_01_Apr_2016_14-16-02.cf5bak
I think it would be much more useful it it was along the lines of:
CFV5_HostFamilyApplication_http---www.globalpittsburgh.org_01_Apr_2016_14-16-02.cf5bak
We already know by the product name and the extension that this is a ChronoFrom backup, so there is no real point to "FormsBackup". Personally, I think "ON" is excessive, but that is part of why I'm asking why the idea was behind the naming scheme.
[product-name-and-version]_[form-name]_[site]_[date].[ext]
A backup I made today was named this:
CFV5_FormsBackup_ON_http---www.globalpittsburgh.org_01_Apr_2016_14-16-02.cf5bak
I think it would be much more useful it it was along the lines of:
CFV5_HostFamilyApplication_http---www.globalpittsburgh.org_01_Apr_2016_14-16-02.cf5bak
We already know by the product name and the extension that this is a ChronoFrom backup, so there is no real point to "FormsBackup". Personally, I think "ON" is excessive, but that is part of why I'm asking why the idea was behind the naming scheme.