To prevent sensitive information such as passwords from being logged in general activity logs, add the following XML chunk to the bottom of opensrf_core.xml, just inside the <config> section:

  ...
  </routers>
  <shared> <!-- new block starts here -->
    <log_protect>
      <match_string>open-ils.auth.authenticate.verify</match_string>
      <match_string>open-ils.auth.authenticate.complete</match_string>
      <match_string>open-ils.auth_proxy.login</match_string>
      <match_string>open-ils.actor.patron.password_reset.commit</match_string>
      <match_string>open-ils.actor.user.password</match_string>
      <match_string>open-ils.actor.user.username</match_string>
      <match_string>open-ils.actor.user.email</match_string>
      <match_string>open-ils.actor.patron.update</match_string>
      <match_string>open-ils.cstore.direct.actor.user.create</match_string>
      <match_string>open-ils.cstore.direct.actor.user.update</match_string>
      <match_string>open-ils.cstore.direct.actor.user.delete</match_string>
    </log_protect>
  </shared> <!-- new block ends here -->
</config>

An updated EDI order template is now part of the stock data. To avoid clobbering potentially functional EDI templates, no upgrade script was included to automatically upgrade existing templates. To upgrade to the newest template:

UPDATE action_trigger.event_definition SET template =
$$
...
$$ WHERE id = 23;

/*
Use the template value for event definition 23 (line 7995) in
950.data.seed-values.sql as the contents (...) of the above command.
*/