Noting for whoever works on this that what distinguishes the provider version from the admin page version is not a whole lot:
<eg-fm-record-editor #editDialog idlClass="acqedi" readonlyFields="id,provider" hiddenFields="provider,last_activity" [fieldOptions]="{ host: {helpText: hostHelpStr}, username: {helpText: usernameHelpStr}, password: {helpText: passwordHelpStr}, path: {helpText: pathHelpStr}, in_dir: {helpText: indirHelpStr}, vendacct: {helpText: vendacctHelpStr}, vendcode: {helpText: vendcodeHelpStr}, account: {helpText: accountHelpStr} }" fieldOrder="id,label,host,username,password,account,owner,path,in_dir,vendacct,vendcode,attr_set,use_attrs"> </eg-fm-record-editor>
If BasicAdminPage were taught hiddenFields as a new @Input and the helpText strings were moved to a shared template somewhere, a new admin interface for EDI Accounts would be nearly as simple as AddressAlertComponent.
Noting for whoever works on this that what distinguishes the provider version from the admin page version is not a whole lot:
<eg-fm- record- editor #editDialog "acqedi" lds="id, provider" s="provider, last_activity" ns]="{
host: {helpText: hostHelpStr},
username: {helpText: usernameHelpStr},
password: {helpText: passwordHelpStr},
path: {helpText: pathHelpStr},
in_dir: {helpText: indirHelpStr},
vendacct: {helpText: vendacctHelpStr},
vendcode: {helpText: vendcodeHelpStr},
account: {helpText: accountHelpStr}
} " "id,label, host,username, password, account, owner,path, in_dir, vendacct, vendcode, attr_set, use_attrs" > fm-record- editor>
idlClass=
readonlyFie
hiddenField
[fieldOptio
fieldOrder=
</eg-
If BasicAdminPage were taught hiddenFields as a new @Input and the helpText strings were moved to a shared template somewhere, a new admin interface for EDI Accounts would be nearly as simple as AddressAlertCom ponent.