report

Vars
access	The access required to view the report.
access_edit	The access required to submit the report. See documentation below.
available_on_ntnet	Whether this report type should show up on NTNet.
creator	The name of the mob that made the report.
fields	A list of fields the report comes with, in order that they should be displayed.
file_time	Time submitted.
form_name	Form code, for maximum bureaucracy.
logo	Can be set to a pencode logo for use with some display methods.
title	The name of this report type.
Procs
add_field	Don't add fields except through this proc.
field_from_ID	Looking up fields. Names might not be unique unless you ensure otherwise.
generate_fields	The place to enter fields for report subtypes, via add_field.
generate_nano_data	If access is given, will include access information by performing checks against it.
generate_pencode	This formats the report into pencode for use with paper and printing. Setting access to null will bypass access checks. with_fields will include a field link after the field value (useful to print fillable forms). no_html will strip any html, possibly killing useful formatting in the process.
set_access	Access stuff. The report's access/access_edit should control whether it can be opened/submitted. For field editing or viewing, use the field's access/access_edit permission instead. The access system is based on "access patterns", lists of access values. A user needs all access values in a pattern to be granted access. A user needs to only match one of the potentially several stored access patterns to be granted access. You must have access to have edit access.
verify_access	Strongly recommended to use these procs to check for access. They can take access values (numbers) or lists of values.

Var Details

var
access
– /list

The access required to view the report.

var
access_edit
– /list

The access required to submit the report. See documentation below.

var
available_on_ntnet
–

Whether this report type should show up on NTNet.

var
creator
–

The name of the mob that made the report.

var
fields
– /list/datum/report_field

A list of fields the report comes with, in order that they should be displayed.

var
file_time
–

Time submitted.

var
form_name
–

Form code, for maximum bureaucracy.

var
logo
–

Can be set to a pencode logo for use with some display methods.

var
title
–

The name of this report type.

Proc Details

proc
add_field
(field_type, name, value, required)

Don't add fields except through this proc.

proc
field_from_ID
(ID)

Looking up fields. Names might not be unique unless you ensure otherwise.

proc
generate_fields
()

The place to enter fields for report subtypes, via add_field.

proc
generate_nano_data
(/list/given_access)

If access is given, will include access information by performing checks against it.

proc
generate_pencode
(access, with_fields, no_html)

This formats the report into pencode for use with paper and printing. Setting access to null will bypass access checks. with_fields will include a field link after the field value (useful to print fillable forms). no_html will strip any html, possibly killing useful formatting in the process.

proc
set_access
(access, access_edit, recursive, override)

Access stuff. The report's access/access_edit should control whether it can be opened/submitted. For field editing or viewing, use the field's access/access_edit permission instead. The access system is based on "access patterns", lists of access values. A user needs all access values in a pattern to be granted access. A user needs to only match one of the potentially several stored access patterns to be granted access. You must have access to have edit access.

This proc resets the access to the report, resulting in just one access pattern for access/edit. Arguments can be access values (numbers) or lists of access values. If null is passed to one of the arguments, that access type is left alone. Pass list() to reset to no access needed instead. The recursive option resets access to all fields in the report as well. If the override option is set to FALSE, the access supplied will instead be added as another access pattern, rather than resetting the access.

proc
verify_access
(given_access)

Strongly recommended to use these procs to check for access. They can take access values (numbers) or lists of values.

report /datum/computer_file/report

Vars

Procs

Var Details

var access – /list

var access_edit – /list

var available_on_ntnet –

var creator –

var fields – /list/datum/report_field

var file_time –

var form_name –

var logo –

var title –