025184: New HHT - MOVE_STOCK_CROSS_SITE option missing
KCSL have enhanced new HHTs to allow for group moves between
sites.
Customer needs the ability to move stock items from one site
to another.
Currently this is achievable via the Old HHTs by enabling
the configuration option MOVE_STOCK_CROSS_SITE within the setup of the HHT
website.
KCSL will add a similar option to allow for cross-site group
moves.
An updated Khaos Control application and changelog will be
provided with this functionality. Once the update is applied, please contact
the Support Team to update the necessary HHT files.
A new HHT option called ‘Cross-site group moves’ can be
found in the HHT [ Options | Options ] screen. To enable cross-site group
moves, tick this option and click ‘Next’ to return to the HHT main screen.
After applying the above
Configuration, typical steps for usage would include the following.
With new ‘Cross-site group moves’
option disabled, group move functionality will not change.
With new ‘Cross-site group
moves’ option enabled, stock can be moved between sites via the HHT.
An example usage with new
option enabled:
- In the HHT, go to Group Moves.
- Input source location and
click next.
- Input stock code and click
next.
- Input quantity and click
next.
- In the ‘Destination
Location’, you may type/scan any unique location across any
site.
- Non-unique location names
will give a warning message, but you can still choose these locations
using the ‘Location Lookup’ screen.
- You can also use the
‘Location Lookup’ screen to filter for specific locations as usual.
- Note that when
‘Cross-site group moves’ is enabled, the ‘Location Selection’ dropdown
now also shows which site a location is in.
- This allows for users to
pick from non-unique location names (e.g. an Arrivals location in
multiple sites).
- Choose your location and
complete group move as usual.
What's New v8.250
This article details the new features introduced in Khaos Control v8.250
025418: Button added to Manual Statement Run to allow sending Related Documentation
1. Overview
KCSL have made further changes to development [025298:
Include credit notes & remittance, with automated debt chasing alongside
statement and invoices, plus change Unallocated Transactions Box] to enable the ability to manually trigger the collation and sending of related documentation
as part of their manual statement run process.
2. Specification
An option has been added to
the right-click context menu of the detail grid within the [ Accounts | Debt
Management | Debtors / Creditors ] screen. This allows the user to send the
current (or green selected range of) customer(s) a statement report that also
includes related documentation, as per the previous development.
Where
a single customer is passed through to this function, a dialog will be
presented (similar to the existing "Email this Doc" / "Auto
Email Option" dialog) allowing the user to select and existing contact /
email or enter an arbitrary email address to send the documents to.
Note the automated process implemented in the previous development 025298 will function as prior and will not impact the existing development or user
experience
3. Configuration
An update and a changelog will be applied as a part of this development, once applied configuration steps are as follows:
4. Usage
- An additional option named "Email
Statements + Associated Docs" has been added to the right click context menu located within [Accounts | Debt Management | Debtors / Creditors] under "Generate Statement" (Fig.1)
- Within the 'Email Statements + Assosiated Docs' dialogue there are two sections. "Email Settings" & "Emailing single Customer" The second of which is only visible when a single entery from the Debtor/Creditor list is selected
What's New v 8.248
Below are details of new features added in this version of Khaos Control
025506 Improve DLL handling more/again
KCSL have enhanced how the KhaosControl.exe
app stores and uses dll files.
DLL handling has been changed such
that DLLStore folders are ignored, and the rules now are:
-A folder is created in
%appdata%\KhaosControl with a name based on the contents of the DLLs, not the
version number
-If this location can't be
accessed, it falls back to a temp folder
-It should therefore be possible
to run multiple dev versions (which contain different DLLs) simultaneously if
necessary
-Whenever KC starts, it writes a
timestamp file into the DLL folder, and only clears down folders where no file
has been updated in the past 30 days, so old folder will be cleared, but not
until they're actually unused
An update will be applied as a part of this development. No
further configuration steps are required.
Once configured steps for usage are as follows:
Users should see no different in how things operate.
