Phoenix v3 build

Now a changeset assign is available in views which we can pass to the form:. Changeset and converts it to a form, which is passed to the function as the argument f.

All the remaining functions in this module receive the form and automatically generate the input fields, often by extracting information from the given changeset.

For example, if the user had a default value for age set, it will automatically show up as selected in the form. If no action has been applied to the changeset or action was set to :ignore , no errors are shown on the form object even if the changeset has a non-empty :errors value.

This is useful for things like validation hints on form fields, e. That changeset isn't valid, but we don't want to show errors until an actual user action has been performed.

Ecto automatically applies the action for you when you call Repo. Changeset struct field or by using Ecto. FormData protocol.

By default, Phoenix implements this protocol for Plug. Conn and Atom. This is useful when you are creating forms that are not backed by any kind of data layer. Let's assume that we're submitting a form to the :new action in the FooController :.

Conn to set input values from the request parameters. Alternatively, if you don't have a connection, you can pass :foo as the form data source and explicitly pass the value for every input:. The functions in this module also support such usage by simply passing an atom as first argument instead of the form.

When working with collections, :prepend and :append can be used to add entries to the collection stored in the changeset. The form generates a CSRF token by default. Your application should check this token on the server to avoid attackers from making requests on your server on behalf of other users. Phoenix by default checks this token. This is to avoid tokens from leaking to third party applications. If this behaviour is problematic, you can generate a non-host specific token with Plug.

LiveView builds on top of this function to provide a function component named form. Inside your HEEx templates, instead of doing this:. Generate a new form builder for the given parameter in form without an anonymous function.

This is used to avoid multiple protocol dispatches. Defaults to "true". The default value is extracted from the form data if available. Warning: this feature isn't available in all browsers. If you want to include the seconds field hidden by default , pass second: [] :. You are also able to configure :month , :day , :hour , :minute and :second. All options given to those keys will be forwarded to the underlying select. For example, if you are using Phoenix with Gettext and you want to localize the list of months, you can pass :options to the :month key:.

The available values can be given in :options. It must be a function that receives a builder that should be invoked with the select name and a set of options. See builder below for more information. Here is an example from EEx:. Although we have passed empty lists as options they are required , you could pass any option there and it would be given to the underlying select input.

This functionality exists mostly for integration with Phoenix. See the Phoenix. LiveView integration section in module documentation for examples of using this function. Automatically inflected when a changeset is given. Defaults to "post".

Required when uploading files. When set to false, this is disabled. This option is only used when a connection is used as the form source and it will make the errors available under f.

If an ID is given, all form inputs will also be prefixed by the given ID. All other options will be passed as html attributes, such as class: "foo". The form should either be a Phoenix. The first argument should either be a Phoenix. Note: if you are a Phoenix for Windows user, please read the following information regarding downloads. Phoenix SQL software patches have been designed in such a way that only the latest available patch is required.

There is no need to install each patch incrementally. Phoenix SQL Patch. Expand all. Collapse all. Note: All changes referenced below in the 4. To help you with the initial population of your proprietary card file Phoenix now provides the ability to download an application that will create an Excel spreadsheet customized to your currently configured setup parameters defined within Phoenix. Contact OPW tech support for further assistance on how to use. Support was added allowing the user to create a configurable custom export template that can be used for future exporting of data.

Application pool change to 2. NOTE : If the user name exceeded 20 characters the new reset password would not allow the user to login. These reports now provide card type grouping and sub-totals.

This update also provides support for older transactions where this data isn't available, allowing a backwards compatibility presentation of the data. Adds another network card type report: "Network Trans By Product" which provides product totals grouped network and card type. New PriceZone feature allows the user to create site-based groups for sending prices to the FSC 1.

This feature also includes support for scheduling price updates. Adds support to capture network card type codes during polling process. All exported files will be saved with the name of the export type followed by the current date e. The date format is based on the regional settings of the Service Engine PC. This modification was added in order for OPW to provide better support to the user. Added two reports allowing support for customers using keyboard entry for Driver Cards by replacing the "Driver Number" with the "Full Name" field for that card.

The new reports are:. A new "Scheduled Poll Log" report was created to show site-polling history based on scheduled events. Added new export format; the Castle. CSV export released in the 4. XLS format. NOTE: Initial generation of the report may take time depending on the date range and amount of data. These problems have been corrected by populating the dropdown with a sorted list of all users, regardless of how many. You may now select the user from the list, fill in the required fields and click Apply; Phoenix SQL will then create the entry in the Address Book for the selected user.

NOTE: User must run the latest patch again on the repaired system to ensure the system is up to date. Two new reports have been created to group transactions by product under the reported card number.

Each group will provide its own product sub-totals for the card. The new reports are called:. When exporting data, the user can now select an option to overwrite an existing export file with the same name, instead of appending the date for each file written.

This allows other software packages to import without manual support every time. Fixed issue where the "Last Used" date was not being updated in the card record when transactions were imported. Fixed issue where Card Backup files failed the import process due to an unexpected character ' in the card record short-name field. A behind the scenes service "Service Engine" was separated into two services new, called Timer Service for better support and maintenance.

The backfile was growing in size by appending the same data. This was resolved by changing the file name to include the time. This allows the next backup to be a new file.

After scheduling report s to print, the selected reports were not being displayed in the list if you tried to edit the scheduled event. Under the "Change config" tab, an issue was found that the default timeoutwas out of range.

Trying to save a different setting failed because the default value was larger than the available range. Issue was found where the pop-up that shows when certain reports are selected where the message displayed did not reflect the actual problem.

Fixed an issue related to the wrong pop-up message being displayed when trying to delete ATG data. Added new card types, for card total report. Updated Manual Transaction editing where the transaction's assigned Account number is changed to reflect the last Driver or Vehicle card number selection.

This allows user to alter a transaction's billed account number. Allow assignment of Single Cards to the Global Cards account. Reversed default transaction view to display most current at top. Modified Fuel Zone deletion to decline request if zone is currently mapped to any card on file.

Updated Password naming on site configuration page to match FSC references. Fixed offline license activation error. Fixed issues related MPG calculations, associated to product settings and duplicated Transaction and Sequence number on same date. Removed "Global Cards" account from dropdown selection under account report settings.

Added new printer tab to view the systems default printer. Fixed export concerns related to spacing and alignment issues. Fixed certain reports that failed to generate due MPG formula error. Fixed Quantity and Price rounding issue during import of polled transactions. Fixed issue where reports selected for landscape printed as portrait. Fixed issue where Service Engine was crashing when log file were changed to network directories. Fixed transaction reprice issue where values less than 1.

Resolved modem connection issues. Fixed column alignment on some reports. Fixed Status reporting issue for scheduler Reprice event. Fixed condition where 5-digit IP port numbers where not supported. Fixed issue when importing incomplete transactions after creating the missing cards. Caused some transactions to be lost. Fixed a resulting issue in date field of custom export where time was always shown as am.

Fixed data validation issue in Tank Reconciliation Report. Resolved issue where FSC command line allowed the configuration of longer password lengths. Changed how Print option is available in reporting module. Type the code from the image. We are using cookies to give you the best experience on our website. For more information, please see our privacy policy.

Before OPW Fuel Management Systems can provide you with a password to unlock the update file, you must have completed and returned the registration form. When calling, you will be asked to provide the name of the registered user, the version of Phoenix you are running i. After you have obtained the password for your version of Phoenix, you can execute the downloaded file by double-clicking on it from within an Explorer window or from the Start menu.

All Rights Reserved. Group Management access rights issue resolved. Managers were allowed edit to transactions outside of site rights. Fixed issues, introduced in previous patch; Database backup failed. Price update under scheduler failed, intermittently. Activity report failed if error in MPG data. Fixed issue in Phoenix Configuration Tool where the Database backup operation could not be disabled from use.

Addressed an issue related to Price Zones and Site Data access rights. Corrected a condition that stopped data exports from running if the "Transactions flagged as; Exported to Fleet" option is selected. Updated custom exports to use a defined file format. Addressed a scheduler issue were reports "linked to Event" did not run after the event to which it was linked completed successfully. Version: 4. You must now enter this when activating Phoenix SQL. To obtain your serial number please contact local distributor to purchase.

Affected reports have been updated to resolve a condition where products not flagged as "Affects MPG" Note: All changes referenced below in the 4. This allows previously exported files to be overwritten when a new file is exported. This features allows 3 rd party software packages to auto import a file with a specific name. Each group will provide it's own product sub-totals for the card. This will allow the user to select how a records date is provided allowing flexibility when imported the data into 3rd report packages.

In support of this, additional parameters required when configuring report to print. Changed reports to have same format, font and sizes. When large quantity values exist in transaction records the report total field was dropping digits from the left.

When attempting to restore a deleted account, if an error message was displayed, the "Ok" button was inactive. If a scheduled "Export Data" event was configured to save the output file on shared network drive, that wasn't was available for use at the time of execution. The affected export file was not created, but the associated records where flagged as exported, stopping them from being provided in a following export event that completed successfully.

This condition caused the exported data files to be missed transactions. When attempting to delete an account without associated cards an error was generated and the account was not deleted. When a "Price Zone" scheduled event fired it did not correctly reflect last status, such as; indicating missed when event completed.

When creating a scheduled event, the "Link to Another" radio button option was not always available for selection, until the event was saved and then selected again for "Edit. Transaction filter options did not work correctly when viewing deleted transactions. Addressed reported issues found in the Excel "Import Card Template" Crystal Report software upgraded from version 10 to Phoenix was mistakenly using transaction sequence as part of card odometer update rule, creating issues for tracking current odometer.

When configuring the scheduler to execute event at regular intervals by hour. Setting the inteval to 24hours stopped scheduler from running. Fixed by limiting interval to 23 hours max. The Single Card option was not available on the Global Account account view page. DVD installation pending , had issues installing on Win Server bit.